...

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

...

•  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

...