...
2) Structure of the panel
- 10-15 min: introduction highlight why we are having panel, what we want to get out of it
- validate ideas/plans - not missing a reqmt from the community or reqmt by external standards
- 5 min or less each: each panelist present backgrounds and views
- a few topic prompts to guide discussion
- how does this plan sync up or create conflicts with your current work?
- linked data - what benefits are there in linked data?
- how to serve common use cases - as everyone repositories evolve? how have people hacked DSpace to get it to do what they want - make sure current plan addresses some of those needs
- what are the priorities and more imminent problems to tackle
- I think it would be nice if we may be able to present a few opposing opinions on the three topics, and see how the audience reacts. e.g.
A new look at supporting and safeguarding standards
Someone who's highly in favor of doing a full migration to dcterms vs someone who presents the idea of a mixed approach where we keep some free text fields like dc.title.
...
Or someone who's in favor of adding custom/institution specific fields vs someone in favor of reusing external schema's like RIOXX or UKETD
Metadata for all:
...
Maybe there's someone who wants to make a case for treating other dspace objects (coll, comms, bitstreams) differently when it comes to metadata?
...
Future proofing
Opposing/different opinions on what the priorities should be?
What do you think? would this make sense? How can we ensure that we "dumb it down" enough so that it appeals and affects the audience the most.
Action Items
- ?
- .
-