- Compact style
- Indico style
- Indico style - inline minutes
- Indico style - numbered
- Indico style - numbered + minutes
- Indico Weeks View
We would like to announce the 5th Invenio User Group Workshop, IUGW2019, to be held as part of Open Repositories 2019 (OR2019) on Monday, June 10th from 09:00-17:00 at the University of Hamburg (main building).
1. First register to Open Repositories 2019 conference: https://or2019.blogs.uni-hamburg.de/registration/
2. Next, register to the Invenio User Group Workshop 2019 on https://www.cognitoforms.com/UniversitätHamburg/OpenRepositories2019WorkshopRegistration
Invenio User Group Workshop (IUGW) is a biennial workshop where the Invenio repository community meet among current and future users and developers from around the world. The workshop consists of a series of tour de table service presentations and talks from attendees related to the Invenio digital repository framework.
Deadline: May 22nd at 23:59 CEST
Acceptance: Notification on May 27th.
The Invenio User Group Workshop 2019 will address a wide range of topics related to the overall theme for Open Repositories 2019:
We are particularly interested in the following themes:
Please circulate this workshop link also among colleagues who might be interested in.
Looking forward to seeing you.
An overview of the current status of Invenio, the community, ongoing projects and future projects.
“JAIRO Cloud” has been provided as the shared repository service in
Japan since 2012 by National Institute of Informatics. In April 2019,
the number of institutional repositories in Japanese universities based
on JAIRO Cloud is exceeded 558, which covers 70% of the number of
institutional repositories in Japan. Nowadays, it has become to be
widely recognized as the institutional repository infrastructure in Japan.
JAIRO Cloud is built using a repository software "WEKO" developed from
scratch by National Institute of Informatics. First version of WEKO is
released in 2008. WEKO has been developed as a content management module
and is characterized by its ease of use and ease of customization. It
has been being developed while reflecting actual user voices of JAIRO Cloud.
On other hand,With the rise of the open science movement in recent
years, the content handled by repository software is becoming more
diverse and bigger than before. As a result, WEKO has been required
scalability and extensibility for supporting diversity of research data.
However, WEKO built on traditional WEB architectures, had difficulty
supporting the requirement. We needed to develop a new generation of
WEKO. Therefore, we compared major open source repository software such
as DSpace, EPrints and Fedora and chose Invenio version 3 for our
purpose and started development of new version of WEKO(hereinafter
called WEKO3).
In this presentation, we will briefly introduce our background, and
introduce the functions, features, problems, and future plans of WEKO3
under development.
The National Library of Technology (NTK) runs two invenio repositories - National Repository of Grey Literature (NUSL; v1.1.2) and instituional repository of NTK (IDR; v1.0.0). The repositories have partly same typology and data models. We have just started on works on upgrade and creating new data model. For now we are discovering which parts are missing and we still need to keep them as e.g. collections and we try to figure out the best and the easiest solution for our repositories what includes revision of whole concept and their funcionalities.
An introduction to JuSER repository as a publication database, and open access repository including authorities for reporting. Includes an overview of APC integration in JuSER reporting.
Currently, JOIN2 uses INVENIO 1.1.7 as base software. JOIN2 is implemented at eight instances and is in use
INVENIO 1.x was preferred over the other systems on the market thanks to its flexibility and general (internal) standardized data model which enables JOIN2 to tackle its broad scope of needs and allows the required easy extensibility. In particular, the huge potential of the implementation of Authority control unearthed entirely new use cases without any major rewrite.
Among the principal characteristics that led to the selection INVENIO 1.x over its competitors: A library system does not allow users to store their private data. CRIS systems are usually not usable as a repository. APC management is not really implemented in either of these.
Given the library background of the JOIN2 members, the MARC-21 data model of INVENIO 1, even with its imperfections, marked a key point in the system selection.
Using the MARC-21 standard as internal format is in our opinion a good basis for our transition to INVENIO 3 and provides a good link between the different functionalities and use cases:
Using MARC-21-Authority based records allows JOIN2 to identify people, grants, experiments, facilities, affiliations and funding information using interchangeable, shared records. Additionally, a shared set of journal records was derived and is maintained. This set profits from the MARC-21 format, which allows reuse and enrichment of data obtained from other library systems using common MARC-21 and RDA concepts. The resulting data can be reused even outside of JOIN2. Adding MARC-21 Holdings enabled JOIN2 to almost seamlessly integrate the library catalogues at DESY and GSI and all functionalities required to handle Article Processing Charges (APCs), a rapidly growing part of our services.
Given the broad scope of research in the JOIN2 instances, JOIN2 profits a lot from bibliographic expertise at the libraries. The knowledge how to model things appropriately can almost immediately be transferred from the librarian to our internal structure using the same language on both ends: MARC-21 and RDA.
To this end JOIN2 proposes the implementation of an INVENIO flavor with a MARC-21 data model as "first class citizen". This would form the base for the new JOIN2 flavor of INVENIO 3.
As formal procedure we suggest to set up an agreement with all interested parties and CERN, from which stems the INVENIO 3 technology.
Besides the obvious content such as title and description of the project, such an agreement needs to specify the deliverables, work packages and milestones with a schedule, together with a description of the organization including roles and responsibilities of all parties involved.
We believe that the unique combination of repository, ILS, CRIS, APC handling and campus literature management targets academic/research institutions and thus has a large market potential. It enables their libraries to run and maintain this crucial infrastructure, hugely benefiting from the synergies we already rely on at JOIN2 today. The field of application is not restricted to research institutes and libraries: the INVENIO MARC-21 flavor and later the JOIN2 flavor of INVENIO 3 will be useful for governmental organizations and companies, too.
We want to contribute to the to-be-defined work packages of this MARC 21 INVENIO 3 flavor.
Please contact us at library@desy.de, if you are interested in joining our efforts to establish first an INVENIO 3 MARC 21 flavor and later a full INVENIO 3 JOIN2 flavor.
Research Data Repository @ Universität Hamburg
Learn how the Invenio RDM will be used to support clinical and translational research through work happening in the CTSA Program National Center for Data to Health and Northwestern University.
The CERN Open Data repository platform manages and disseminates close to two petabytes of open data from particle physics. This includes collision and simulated datasets together with software code examples, associated documentation, configuration files, and virtual machines enabling to explore the released data for both educational and research purposes. In this talk, we will address how Invenio technology is used in running the service, form managing big research data sets, through keeping the system highly available during high user demand periods, up to providing customised interactive data visualisation and exploration of research data.
https://gitlab.cern.ch/invenio/template-openshift
The presentation will show some insights about the migration from Invenio 1 to Invenio 3. It will include some real examples with focusing on data management and architecture challenges.
Short presentation (from a software developer's point of view) of the process of developing the new Repository starting from zero.
There are two main projects based on Invenio v3 at RERO currently, both under active development: RERO ILS and SONAR. RERO ILS is an Integrated Library System, and it includes two sub-projects, RERO-EBOOKS and MEF (Multilingual Entity File). The second main project, SONAR, is a Swiss-wide institutional repository that intends to collect, promote and preserve scholarly publications of authors affiliated with Swiss public research institutions. It aggregates publications from various sources, including existing institutional and subject repositories. SONAR also provides IRaaS (Institutional Repositories as a Service).
What are the realizations and lessons learned?
Invenio at CottageLabs
An enterprise search as a service solution based on Invenio 3
Citations and COUNTER-compliant Usage Statistics
CERN has partnered with 10 multidisciplinary institutions and companies to build a turn-key open source research data management platform called InvenioRDM, and grow a diverse community to sustain the platform.
The InvenioRDM project is funded by the CERN Knowledge Transfer Fund, as well as all the participating partners, including:
The project has an ambitious one year schedule in which it will deliver:
The key to successfully achieving the ambitious schedule is that InvenioRDM will be based on Zenodo that have already been successfully validated over the past 5 years.
Our vision in the next five years, is to make InvenioRDM a world-leading extensible research data management platform used by research institutions all around the world and with businesses providing services, support and customizations on top of InvenioRDM.
Join us for an open discussion on open source community building and how to empower your local engagement efforts.
Open discussion about how to empower the Invenio community.
Closing notes