Date

Call-in Information

Time: 08:00 am, Eastern Time (New York, GMT-04:00)

To join the online meeting:

  • https://lyrasis.zoom.us/j/82670709536?pwd=MzF3NDladE1DKzEvUml4SGQ5eUFsQT09

    Meeting ID: 826 7070 9536
    Passcode: 008047
    One tap mobile
    +16699006833,,82670709536#,,,,*008047# US (San Jose)
    +19292056099,,82670709536#,,,,*008047# US (New York)

    Dial by your location
            +1 669 900 6833 US (San Jose)
            +1 929 205 6099 US (New York)
            +1 253 215 8782 US (Tacoma)
            +1 301 715 8592 US (Washington DC)
            +1 312 626 6799 US (Chicago)
            +1 346 248 7799 US (Houston)
            877 853 5257 US Toll-free
            888 475 4499 US Toll-free
    Meeting ID: 826 7070 9536
    Passcode: 008047
    Find your local number: https://lyrasis.zoom.us/u/kbEatBA0od

Slack

Attendees

(star)  Indicating note-taker

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

Agenda

  1. Massive migration of data from DSpace to VIVO
    1. Further discussion about solution architecture
      1. integration of data in elements of VIVO graph (publications records, researchers, etc.)
    2. Reporting about implementation

Notes

Jose presented his progress. He noticed that Community in DSpace might contain subcommunities, but it is not supported in the Java model. Abhishek confirmed that this situation is possible and quite often in DSpace. Jose should create an example for this Community hierarchy, and Michel Héon will update the YAML model and generate new Java model after that. Dragan Ivanovic thinks we should try to focus the effort taking into account available human resources. Michel Héon suggested to try to work only on DSpace items, to try to integrate those items in the VIVO graph. Jose should implement firstly getAllDSpaceItems for different versions of DSpace (7, 6, 5). Jose will probably base his implementation on REST api for DSpace 7, and on OAI-PMH for DSpace 6 and 5. Michel Héon will design architecture for mapping a DSpace-person to VIVO-person. 

See:

  1. Architectural proposition
  2. About DSpace rdfizer
  3. About an Item in DSpace
  4. DSpace-VIVO GitHub Repo

Task List

  • Michel Héon Implementing DSpace-item in VIVO UI
  • Michel Héon Desing architecture for mapping a DSpace-person to VIVO-person
  • Jose to define an example of Communities hierarchy and to share that with Michel
  • Michel Héon Adapt the DSpace-Item representation in the dspace-vivo exchange data schema (DVExDS) according to José's requests
  • Jose to continue working on getting allDSpaceItems request for DSpace 7, 6 and 5.
  • Abhishek to check whether all options for harvesting are possible for implementation from the perspective of model and APIs of DSpace

Previous tasks 

  • Dragan Ivanovic to define options for harvesting data from DSpace in a wiki page 
  • All to think about the name for middleware internal data structure defined for the needs of massive migration of data from DSpace to VIVO
  • Michel Héon I propose the name 'dspace-vivo exchange data schema'.
  • Jose to continue working on his implementation in accordance with defined options for harvesting data
  • Jose to rename packages in his implementation,
  • Michel Héon to do the same for his contributions
  • The work is completed and the dev-heon branch has been merged by hand into the github repo
  • Michel Héon to think about stronger integration of migrated data in the VIVO graph, and how those data might be linked for synchronization in the case of modification
  • Dragan Ivanovic to make consultation with Abhishek about moving meeting for one hour, and if Abhishek agrees, Dragan Ivanovic will send new ics file. 
  • Michel Héon to prepare and share slides for discussion about architecture
  • Michel Héon and Jose to set up environment, i.e. to install DSpace 7, DSpace 6 and VIVO 1.12.x, Abhishek to help them with DSpace if necessary



  • No labels