Last edited 2 months ago
by Anna Lionetti

ShareVDE:Activities: Difference between revisions

mNo edit summary
mNo edit summary
Line 10: Line 10:
The section [[ShareVDE:Members/Share-VDE working groups|Share-VDE working groups]] outlines the '''main goal for each group''', the current members and the practical info to participate in each work strand.
The section [[ShareVDE:Members/Share-VDE working groups|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==
==Latest achievements==
<span style="color: #000000">Th</span><span style="color: #000000">e '''summary of SVDE achievements over 2019''' can be consulted here </span>[https://drive.google.com/file/d/1v_djkhx_t5F1faexrlC7Y54EMzH6lsX7/view <span style="color: #1155cc">Share-VDE achievements 2019-12.pdf</span>].
<span style="color: #000000">Th</span><span style="color: #000000">e summary of SVDE achievements over 2019 can be consulted here </span>[https://drive.google.com/file/d/1v_djkhx_t5F1faexrlC7Y54EMzH6lsX7/view <span style="color: #1155cc">Share-VDE achievements 2019-12.pdf</span>], while '''some of the major progresses in 2020''' are described below.


In 2020 much work has been carried out.  
In 2020 much work has been carried out, 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:


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)
* Infrastructure & Architecture
*SVDE Frontend (Frontend components, APIs development, SVDE portal and J.Cricket search functions)
* SVDE Backend (Database and Indexing, APIs development)
*APIs for Penn and other skin portals
* SVDE Frontend (Frontend components, APIs development, SVDE portal and J.Cricket search functions)
*J.Cricket Cluster Knowledge Base editing functions
* APIs for Penn and other skin portals
* J.Cricket Cluster Knowledge Base editing functions


The [http://bit.ly/Share-VDE_UXdesign_20190628 design of the UI] has been completed and enhanced by the activities around the J.Cricket Cluster Knowledge Base editor, the requirements for the University of Pennsylvania localisation and for the Kubikat-LOD parallel project.
The [http://bit.ly/Share-VDE_UXdesign_20190628 design of the UI] has been completed and enhanced by the activities around the J.Cricket Cluster Knowledge Base editor, the requirements for the University of Pennsylvania localisation and for the Kubikat-LOD parallel project.

Revision as of 17:06, 10 December 2020


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.

In 2020 much work has been carried out, 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

The design of the UI has been completed and enhanced by the activities around the J.Cricket Cluster Knowledge Base editor, the requirements for the University of Pennsylvania localisation and for the Kubikat-LOD parallel project.

The backend infrastructure has been rearranged to respond to many layers and complex search logic.

The 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).

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