DSpace 7 Upgrading / Configuring / Customizing workshop (Tim, A=
rt & Andrea) (for Users =E2=80=93 Repo Mgrs and Deve=
lopers). (Presenters: Tim Donohue, Art Lowel, Andrea Bollini=
)=20
This will be two 1/2 day workshops:=20
First 1/2 day will concentrate on DSpace 7 from a "technician" perspect=
ive. How to install /upgrade / configure DSpace 7. How to do minor cu=
stomizations 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.
:tick: DSpace + Docker Workshop (Terry & Pascal). How to demo/play/develop with DSpace in Docker (both DSpace 6 and 7).&=
nbsp;(Presenters: Terry Brady & Pascal Becker)
Ideally this would not conflict with main DSpace 7 workshop, or we'd fi=
nd a way to tailor each to different audiences.
Possible OR2019 Talks=20
General "Introducing DSpace 7" talk (Tim). What'=
s in DSpace 7? Higher level overview, flashy demo, references to other "dee=
p dive" talks. (Presenters: Tim Donohue)
DSpace 7 - The Power of Configurable Entities (Lieven). Overview of new feature, how to configure & customize your DSpa=
ce via Entities (Presenters: Lieven Droogmans)=20
a DSpace-CRIS 7 talk is expected as continuation of the Configurable En=
tities talk
DSpace 7 - Enhanced Submission & Workflow (Andrea & Giu=
seppe). Overview of new features & deeper dive on config=
uring/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), Giuse=
ppe Digilio, Terry Brady (Docker), Tim Donohue)
DSpace 7 - New Angular User Interface (Ignace & Art) &=
nbsp;Overview of new UI from a functional perspective, and highlig=
ht the power of Angular. (Presenters: Ignace Deroost / Art Lowel)<=
/li>
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 n=
ow 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 (4S=
cience)to understand whether we can move forward with parameters for no=
w, and update this contract/implementation later. It's unclear to the=
team why these three tickets are blocked for Spring Data REST alignment, w=
hile others that involve links/associations (e.g. PR#37 (Item CRUD) and PR#38 (M=
etadata Registry)) were approved.
Should we consider fixing all these implementations to better align wit=
h Spring Data REST recommendations (perhaps in a future Ticket/PR)?