ShareVDE:Activities

This section is dedicated to Share-VDE activities. If after clicking on a link to a page or a file you are requested to input your credentials, it means that the resource is available to Share-VDE members only.

Useful documentation

For new members, useful tools and information describing the main procedures and practicalities to get on board Share-VDE can be found in the Share-VDE onboarding set.

To have an overview of the major documents currently under analysis, see the document summary. Some of the documents listed are under revision, as they stem from the initial Research and Development phase of Share-VDE.

The section Share-VDE working groups outlines the main goal for each group, the current members and the practical info to participate in each work strand.

Latest achievements

The summary of SVDE achievements over 2019 can be consulted here Share-VDE achievements 2019-12.pdf, while some of the major progresses in 2020 are described below.

The British Library and the Library of Congress officially joined SVDE. The list of SVDE members can be consulted on Share-VDE institutions.

The SVDE IT team has been restructured and enlarged in order to cope with the increasing complexity of the developments, meet the needs of the community and interconnect with several projects. Five main development sub-teams:

• Infrastructure & Architecture
• SVDE Backend (Database and Indexing, APIs development)
• SVDE Frontend (Frontend components, APIs development, SVDE portal and J.Cricket search functions)
• APIs for Penn and other skin portals
• J.Cricket Cluster Knowledge Base editing functions (example of function merging two author clusters in one)

As far as the front-end infrastructure, the graphical and navigational prototype of the new SVDE portal has been completed and was enhanced by the activities around the J.Cricket Cluster Knowledge Base editor (see below), the requirements for the University of Pennsylvania localisation and for the Kubikat-LOD parallel project. Based on this enhanced prototype, SVDE IT team is working on connecting the new components of the frontend of the SVDE platform (https://share-vde.org/) with the backend infrastructure and also with the ad hoc localisation for the University of Pennsylvania. The other skin portals foreseen are being prepared.

A complex diagram of the frontend development project has been created and will be used to generate and display SVDE portal and the connected skin portals and tenants such as Kubikat-LOD, Penn’s localisation, the other skin portals etc. The naming of the infrastructure components in the diagram are arbitrary and respond to the metaphor of a big forest: it’s a way to avoid ambiguity within the various development teams working on SVDE. The names of the skins and tenants for users outside the development teams will reflect the names of the institutions. Please note that it’s a work in progress populated with a few placeholder data for demonstrative purposes; for this reason it might be unstable, it reflects the search and navigation functions though.

A preview of how the new portal will look like is available at http://bit.ly/Share-VDE_UXdesign_20190628.

As far as the back-end infrastructure, the enhancements of the new user interface increased the dependencies between the features specific to each localisation of the SVDE frontend (i.e. SVDE general interface, Penn localisation, J.Cricket module, Kubikat-LOD project etc.) and the underlying system components common to all of them, for example the search logic. This implied the revision of the SVDE backend infrastructure in order to respond to many layers and complex search logic.

Pa <meta charset="utf-8" /> rallel work is being done on the Kubikat-LOD localisation of art libraries: Samhæng has designed the advanced specific prototype with ad hoc features, that is available here https://bit.ly/Kubikat_UI_2020-07-16, and SVDE IT team will implement Kubikat-specific features. This is the result of the joint work of the Kubikat group of libraries that are envisaging a new tool for scholars, researchers and end users as well as for librarians to manage bibliographic resources.

In <meta charset="utf-8" /> the context of AIMS-CKB groups (see below), SVDE has prepared the ground for J.Cricket Cluster Knowledge Base Editor and authority services developments: the design of the editor module has been completed as far as functions for user interaction with the module itself. SVDE IT team is currently working on a detailed analysis of authentication and permission functions. This is key for J.Cricket editing functions (e.g. definition of roles for users and actions that they can perform), but it’s also functional to SVDE in general as far as interaction with other skin portals/tenants is concerned.

Co <meta charset="utf-8" /> nnected to authority services and interaction between SVDE and external sources, the PCC has launched the PCC Wikidata pilot. This pilot might be beneficial to SVDE enhancements concerning Wikidata (see details in the AIMS chapter), and Casalini Libri is taking part in the pilot with reference to SVDE, see the project page on Wikidata Casalini Libri. SVDE-Wikidata Interaction.

SV <meta charset="utf-8" /> DE team has been working on the procedure to fully automate the workflow for receiving updated MARC data from all SVDE member institutions. After the initial import of the MARC full catalogue of SVDE libraries done in 2019, the procedures for the ingestion in SVDE of subsequent regular updates of MARC data have been created and constantly refined for processing, enrichment and clustering in SVDE. The process has been tested using records from a few SVDE libraries that contributed to this test phase and we have set up an automated workflow for collecting regular updates of MARC records.

Th <meta charset="utf-8" /> e import of the full catalogues of the National Library of Norway and of the National Library of Finland has been impacted by the entity model discussion that is being carried on in the Sapientia Entity Identification Working Group.

SV <meta charset="utf-8" /> DE participates to Linked Data for Production 3 project with two major tasks:

1. bu <meta charset="utf-8" /> ild two-ways flow APIs to connect SVDE and Sinopia BIBFRAME cataloguing module. The first step has been done, i.e. the Sinopia team has built an API pipeline that pulls records built by Sinopia and the functioning has been tested by the SVDE team. Moreover, SVDE has analysed Sinopia documentation on the structure of records output from Sinopia: this will be the basis for SVDE to build the connector to import Sinopia records in SVDE. The initial sketch of how SVDE is envisaging to close the loop is available;
2. pr <meta charset="utf-8" /> ovide the conversion and housing of PCC data in an ad hoc PCC data pool working as autonomous tenant, with a separated enriched CKB and ad hoc PCC URIs with dedicated namespace. As the first step, at the beginning of 2020 SVDE will deliver PCC records converted in BIBFRAME along with the original MARC records enriched with URIs.

<meta charset="utf-8" /> Th <meta charset="utf-8" /> e recent initiatives, events and presentations are collected in the section dedicated to articles and resources.

<meta charset="utf-8" /> Th <meta charset="utf-8" /> e Cluster Knowledge Base is being enhanced with new attributes and new controlled vocabularies as a result of the UI design and the revision of the backend infrastructure.

A tenant architecture is being implemented to assure benefits from cooperation without forgetting the autonomy of the libraries (e.g. Penn and National Bibliography future skins; Kubikat tenant).

Working Groups

The design of the manual functions of the J.Cricket Cluster Knowledge Base Editor has been done within the Cluster Knowledge Base (CKB) Editor working group.

We have completed the analysis of authority services within the Authority Identifier Management Services (AIMS) working group. Along with that, we are analysing the integration with Wikidata and ISNI in AIMS and CKB working groups.

We have revised the entity model with the Sapientia Entity Identification (SEI) working group, that is a four layered adaptation of BIBFRAME comprising the entities svde:Opus | svde:Work | svde:Instance | svde:Item. This structure ensures interoperability with other environments using LRM-based models or pure BIBFRAME models.

Current goals

Coming soon

Roadmap

Coming soon

Events and conferences

Coming soon