DSpace 7 Upgrading / Configuring / Customizing workshop (Tim, Art & Andrea) (for Users – Repo Mgrs and Developers). (Presenters: Tim Donohue, Art Lowel, Andrea Bollini)
This will be two 1/2 day workshops:
First 1/2 day will concentrate on DSpace 7 from a "technician" perspective. How to install /upgrade / configure DSpace 7. How to do minor customizations like header/footer/theme changes.
Second 1/2 day will concentrate on DSpace 7 advanced customization (for developers). How to enhance the UI via Angular. How to use the REST API, etc.
DSpace + Docker Workshop (Terry & Pascal). How to demo/play/develop with DSpace in Docker (both DSpace 6 and 7). (Presenters: Terry Brady & Pascal Becker)
Ideally this would not conflict with main DSpace 7 workshop, or we'd find a way to tailor each to different audiences.
Possible OR2019 Talks
General "Introducing DSpace 7" talk (Tim). What's in DSpace 7? Higher level overview, flashy demo, references to other "deep dive" talks. (Presenters: Tim Donohue)
DSpace 7 - The Power of Configurable Entities (Lieven). Overview of new feature, how to configure & customize your DSpace via Entities (Presenters: Lieven Droogmans)
a DSpace-CRIS 7 talk is expected as continuation of the Configurable Entities talk
DSpace 7 - Enhanced Submission & Workflow (Andrea & Giuseppe). Overview of new features & deeper dive on configuring/customizing/using (Presenters: Andrea Bollini & Giuseppe)
DSpace 7 - Open for integration. REST API talk (Andrea) (Presenters: Andrea Bollini)
DSpace 7 - High quality software. Developer best practice (DEV Track - Andrea) (Presenters: Andrea Bollini (lead), Giuseppe Digilio, Terry Brady (Docker), Tim Donohue)
DSpace 7 - New Angular User Interface (Ignace & Art) Overview of new UI from a functional perspective, and highlight the power of Angular. (Presenters: Ignace Deroost / Art Lowel)
Giuseppe says this wIll be ready for final review by Monday, January 14. He will ping us
ACTION: Anyone who has added past comments (that are now fixed), please go in and resolve your past comments once you've verified the fix. That'll help us figure out what is outstanding (if anything)
ACTION:Tim Donohue will reach out to Andrea Bollini (4Science)to understand whether we can move forward with parameters for now, and update this contract/implementation later. It's unclear to the team why these three tickets are blocked for Spring Data REST alignment, while others that involve links/associations (e.g. PR#37 (Item CRUD) and PR#38 (Metadata Registry)) were approved.
Should we consider fixing all these implementations to better align with Spring Data REST recommendations (perhaps in a future Ticket/PR)?