...
- Amy Lana
- @Augustine Gitonga
- xBram Luyten (Atmire)
- Bharat Chaudhari
- Ciaran Walsh
- Claire Bundy
- @Dibyendra Hyoju
- Elin Stangeland
- xIryna Kuchma
- James Evans
- Jim Ottaviani
- Leonie Hayes
- xUnknown User (mpwalsh)
- @Roger Weaver
- xSarah Molloy
- Sarah Potvin
- Sarah Shreeves
- xSue Kunda
- Yan Han
- xValorie Hollister
Discussion Items
...
2) Review of DSpace Functional Overview
- ok with "To be categorized" or misc category
- create new category "architecture"
- 11.4 System Design
- 11.5 Data Model
- create new category "Licensing" or put under "Getting new content into DSpace"
- move 11.2 Creative Commons Support
- move to User Accounts
- 11.3 Subscriptions
3) Vision Group survey review
- Bram: more a statement of a problem than showing answers - than necessarily a change direction
- Maureen: need to move away from out-of-box, extension, etc distinction; need an importance scale rather than how will be implemented; what needs to be turnkey/core to DSpace - where are areas that are ok to plug in to DSpace; not everyone will know whether it should be in/out of the box
- Val: what needs to be easy/non-event, implementation
- Maureen: core svc or functions, currently can be integrated and future integration; definitely need to have, nice to have
- Bram: support for non-English lanuages
- Val: what has to be in DSpace/what does your institution need/absolutely critical in order for me to deliver svcs at my instituitons vs. what would be nice to have vs. what do we need to consider for the future vs. what do we not need vs. don't know?
- Val: important to add ?s about other repository questions that Sarah P. posed - gauge why people are using / looking to use other repositories
4) Metadata project update
- DCTerms is now included in 4.0 - not integrated anywhere, can be used, but must be added to forms, etc.
- Will start to create necessary tools to facilitate migration - have one volunteer to help test tools
- Identify all the places in DSpace where field is hardcoded - make them configurable, but still have them link to hardcoded - will make migration easier
- can be non-developer
- volunteers have helped to identify questions that we haven't thought of - makes us more aware of reqmts people have - negative dates, etc.
- next mtg time: team will figure out
5) JIRA discussion
Action Items
...