Page History

...

• (add your name here)

Meeting Notes

...

DSpace new UI

Q: Can you talk more about the backend? (Ivan)

...

A: Custom JSON format in Angular 2. May have some editor for that specific format . UI devs are in touch with Angular devs, so may ask about that (ng-translate group).

DSpace-CRIS part

Q: How modular is it? If I don’t want CRIS only ORCID integration (Monika)

A: Question of development priorities and cooperation. In case of ORCID, not possible because the plain DSpace data model doesn’t contain it.

Q: Discussion point – do we want to move towards the multiple objects and relationships model in DSpace? Where does the repository stop and CRIS start? (Tim)

A: Andrea – the data model is not specific just to CRIS, any entities/relationships cane modelled.

Q: If I want to try DSpace-cris, is it possible to go back to DSpace? (?)

A: The data model is flexible, but we need to agree on a specific data model to have a common vocabulary of entities in order to be able to exchange content.

Q: We just need an entity for a person – advisor (in order to list theses they advised) (Monika)

A: The model is very flexible (Susanne). Is it really necessary? (Monika) There could be various profiles with various entities (ETDs, scientific). You really need at least three entities even for ETDs (item, person, org. unit). These are increasingly useful also because of H2020, RIOXX requirements. (Andrea)

Q: What could be other possibility? ORCID, author profiles (Pascal)

A: What are the use-cases we need to support in dspace? Could be useful for some of the enhancements we want. If data model supports it, we could use it in a particular use case, not in another (Graham). We’ve been abusing different fields because we didn’t have a proper representation in the model. (Terry)