Page History

...

• DSpace New UI Initiative and Roadmap to DSpace 7 (Presented Slides at http://www.slideshare.net/tdonohue/new-ui-update-or16-developer-dcat-meeting)
  
  • How we got here (DSpace UI Prototype Challenge , also see YouTube playlist of video updates)
  • Why Angular 2? (Risks vs opportunities)
  • Proof of concept: https://github.com/DSpace-Labs/angular2-ui-prototype
  • DSpace 7 proposed architecture (overview), including necessary REST API enhancements
  • How you can help / How would you like to help
    • How can DCAT support this initiative / provide feature suggestions/expertise?  How can other developers / institutions get involved?
• DCAT, Committers and Steering/Leadership: How we collaborate and make decisions togethertogether  (NOTE: Unfortunately, we ran out of time and never got to this topic)
  
  • Streamlining the ways to get new features approved and into DSpace
    • Which features should be pushed up for DCAT or Steering approval first?
  • Moving the code through technical approval process. Are there ways to streamline?
  • Streamlining the ways we share expertise / contributions between and within our groups?

...

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 (ng2-translate group).

DSpace-CRIS

...

discussion

Presentation from Andrea Bollini at Cineca

• DSpace-CRIS has attracted a lot of attention, especially in Europe
• You can always fall-back to a default DSpace installation by just turning "off" the CRIS extension
• The core of DSpace was not touched by this extension. It just adds more objects and functionality
• Began in 2009 with DSpace 1.5.  In 2012 it was open sourced (DSpace 1.8.2), and has stayed parallel to DSpace ever since
• Only supports JSPUI (but will be moving to the new UI alongside DSpace in version 7)
• Some features:
  
  • Deduplication feature coming in next version of DSpace-CRIS
  • "Most Cited" (in SCOPUS, WoS, etc). Just needs your Scopus/WoS key
  • Deep ORCID integration
  • New objects: Author, Organization, Project, etc

Q&A on DSpace-CRIS

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, deep integration not possible because the plain DSpace data model doesn’t contain an "entity" for an Author.  DSpace does represent EPersons, but these are not the same as an Author.

Q: Is it possible to modularize DSpace-CRIS instead of having a separate software as it is now?

A: Yes, but to to so we need to agree on a data model.  We need to decide which "entities" make sense to represent for all DSpace sites (e.g. Authors) and which may only be necessary for extra CRIS-like functionality.  This may allow us to more easily switch on/off CRIS-like features as desired

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 can be modelled.
A: Don't look for the data model, but look for the user perspective. The data model has to fit the desired use cases/featuresA: 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: REST is an opportunity. DSpace-CRIS 7 will definitely, absolutely not be on JSPUI. It will be on DSpace 7 UI. We want separation of layers. (Andrea)
A: New UI is a big opportunity to bring DSpace-CRIS and DSpace back together. We'll now have both building off of the same UI, etc.