Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Dragan Ivanovic 
  2. Michel Héon
  3. Jose Ortiz
  4. Abhishek Raval

Notes

Michel Héon and Dragan Ivanovic discussed different aspects of crosswalks. Michel Héon is afraid only integration with VIVO in read mode is feasible for the first phase of the project, meaning migration of data from DSpace to VIVO, and periodical update of records.  There is a problem with Person entities, in DSpace list of authors are in a string, there might be different variation of names (e.g. Michel Heon, Heon Michel, M. Heon, etc.). If we want to harmonize that, a person identifier is needed. One solution is to do that manually, but requires a lot of effort for some big DSpace databases. The simplest implementation for this manual work is adding a personIdentifier field in the DSpace, and it will be used in the first phase. A little more complex solution is adding a vocabulary of name variants. This vocabulary might be manually maintained or by developing some AI tool for matching variation names to one representative.  The third solution is to make it inaccurate by using some stringToIdentifier approach, in this case variation of names will be completely ignored. 

Dragan Ivanovic reminds that the main point of the first phase of the project is to attract attention of the community, and hopefully to make them interested to fund the next phase. A crowdsource funding might be organized similarly to DSpace Development Fund (https://duraspace.org/introducing-the-dspace-development-fund-ddf/). For that reason, we need a really effective demo of what is done. One scenario might be integratio with a VIVO of a clear and accurate small DSpace repository (10-20 items prepared for this purpose). The another scenario might be integration of https://demo7.dspace.org/ with VIVO.  Abhishek presented how those data might be migrated to local instance of DSpace for experimenting. However, the another solution might be attaching harvester to this endpoint (without using local DSpace instance) - https://api7.dspace.org/server/oai/request?verb=Identify.

Michel Héon believes he might have a demo with more data ready for the next meeting (Thursday 5th of May). For that purpose Jose's harvester should be merged in the main branch. Dragan Ivanovic will send a message to Jose with request to merge his contribution to the main branch until the Monday 2nd of May. 

Dragan Ivanovic asked Michel Héon when might be the right moment for presentation of the project to the VIVO tech IG. Michel Héon thinks it might be Tuesday 10th of May. It should be an effective presentation with the idea to collect the feedback from the group for the improvements of our approach and implementation. 

See:

  1. Architectural proposition
  2. About DSpace rdfizer
  3. About an Item in DSpace
  4. DSpace-VIVO GitHub Repo
  5. Crosswalk - https://docs.google.com/document/d/1waKCEaeEVRO6S1XUX8QmcACH-hZlZFLMZf0masDOx4o/edit?usp=sharing

Task List

  •  Dragan Ivanovic will send a message to Jose with request to merge his contribution to the main branch until the Monday 2nd of May. 
  •  Jose will complete the harvester implementation and merge his PR to the main branch
  •  Jose will check whether his harvested is capable to harvest DSpace items from the open demo server (https://api7.dspace.org/server/oai/request?verb=Identify).
  •  Michel Héon will work further on transforming and loading the data to the VIVO instance. 

Previous tasks 

  •  Dragan Ivanovic to review PR
  •  Jose to improve dspace docker related scripts
  •  Michel Héon will try to work with data coming from a DSpace, meaning not to use only transformation and loading, but also extraction (harvesting) implemented by Jose.
  •  Jose to work on harvesting other elements of model (Community, Collection, etc.)
  •  Jose to write a script for running DSpace Docker
  •  Michel Héon to work on ingesting of DSpace items in the VIVO graph, at the beginning it will be tested through SPARQ query, later added in the VIVO UI.

...