...
| Time | Item | Who | Notes |
|---|
| 10 min | News / announcements / events, etc. | Val | - News
- Webinar recordings
- Upcoming Events
- Other?
|
| 40 min | JIRA discussion | Val | |
| 10 min | Metadata project | Sarah P, Maureen, Bram | - Did metadata team meet on Oct 29? (notes from Sept mtg: Metadata Team Sept 30, 2013)
- Feedback on Richard Rodger's metadata mapper tool in 4.0?
- Update on actions - preparing for review groups (task & finish) to provide feedback on 1) on all mapping and 2) project staging
- identify more people for review groups
- volunteers: Jessica Lindholm, Monica Rivero, Asako Shiba, Yanan Zhao
|
Discussion Notes
1) news
- add next 3 mtg dates to mtg agenda - send out every 6 months a notice on all the months
- ask questions / hold discussions in advance of the mtg - which DSpace feature is on your priority list, then add to the agenda for everyone else to chat about
- new UI: demo.dspace.org.jspui
- OR call for papers - Leif Longran DSpace user group chair
- Elin's - May conf in Univ of Athens
- SPARC Open Access - March - user group mtg?
2) JIRA
| Jira |
|---|
| server | DuraSpace JIRA |
|---|
| key | DS-1630 |
|---|
|
Document delivery form - for metadata only items. DCAT views it as a non-standard use case. Better way would be to add document and put embargo on it and then add the new "Request Copy" feature. Bram to put DCAT comments in and recommend closing issues.| Jira |
|---|
| server | DuraSpace JIRA |
|---|
| key | DS-1500 |
|---|
|
This is really an external development project. May be able to make some progress on an integration using new REST API in 4.0 and SWORD. Needs are not clear. Val to write in JIRA.| Jira |
|---|
| server | DuraSpace JIRA |
|---|
| key | DS-1451 |
|---|
|
plagurisum check. would dspace check stuff coming in or to use stuff in dspace to check against other things - expose dspace so that it can be easier to do plaguriusm checks. could be people interested. first step is to work out way to offer dspace items to other sources that can do plag checking, so that you can work with existing tools – check against dspace content rather than incorporating into dspace directly. instead of putting up on a faculty website - you are protecting yourself against plag. rather than intergrating plag systems into dspace directly, instead provide hoods so that other existing svcs can look at dspace. if you want plag checking in your dspace repo - run agains your repo. unclear how plag systems look for info. repo mgr shouldn't have responsibility for plag at time of submission. done externally from dspace - not a part of dspace. Bram will write it.3) metadata
Bram met at Sarah P discussed at DLF last week
Action Items
- DS-1678: EZID DOI - related to DS-1535 - likely of interest of the community - issue closed/fixed and included in 4.0
- DS-1679 should be higher priority (ELIN) - issue closed/fixed and included in 4.0
- DS-1453 repository content analysis - post summary of preliminary DCAT discussion on JIRA issue and also post a msg to DCAT list to encourage members to create a bucket list of what they would like to see (ALL)
- DS- 824 Request Copy function for XMLUI - Sarah to contact Texas developers to see if any further work has been done and also solicit possible resource to help review Univ of Minho/UofM code, Jim will f/u with Ivan to see what help (from Texas or others) may be useful (SARAH P., JIM) - PR - appears to be in 4.0?
-
Metadata project - prepping for review group (Metadata team - Sarah P., Bram, Amy, Maureen)
- revised proposal page - archive previous page
- add link to OR13 preso on proposal page
- clean up the preliminary DC mapping
- look at other applications using DC - Omeka uses unqualified DC, others?
- think about / ask others about who could participate in review groups