Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


Discussion Notes/References

 

2) JIRA review

  • DS-1602 (Ivan/cmtr request fro DCAT input): Some metadata is not exported through OAI with oai_dc - "We'd love to hear comments from the DC standardization working group in DCAT about what is actually needed in this respect, in light of the proposed migrations. (Note: this will affect also other metadataPrefixes besides oai_dc, but DCAT doesn't have to worry about that.)"
    • Elin: I think needs for OAI output on DC depends on the fields. It would be useful to see a list of the fields that are currently not included? If a list is not available, then a general fix that enables all DC fields to be exported would be preferred. 
    • Ivan: I can tell you the list of all fields currently included. Fields not included would be those which have been locally defined and one intentionally excluded (dc.description.provenance) administrative field. If anything else is missing, it's an omission we should fix. Following Sarah Potvin's comment in Jira, I accepted the change. This was the actual change: https://github.com/DSpace/DSpace/pull/258/filesSo you can see the current list of published oai_dc metadata (after the change) here: https://github.com/DSpace/DSpace/blob/master/dspace/config/crosswalks/oai/metadataFormats/oai_dc.xslI'm not so familiar with the proposed set of metadata fields that should be in 4.0, so if any metadata field from 4.0 is missing in oai_dc.xsl (which is a mapping of DSpace metadata to oai_dc), we should add it.

  • DS-1204(Ivan/cmtr request fro DCAT input): Submissions page should display Workflow Tasks before Archived Submissions
    • Elin: I don't know the xml UI very well, however this seems to indicate that you get a listing of submissions and archived submissions at the top (unlike the JSP UI). For users who submit a lot, I think this would get in the way so agree that a shift towards the bottom of the page would make sense.
  • DS-1453 (Ivan/cmtr request fro DCAT input): repository content analysis - "This issue serves to collect requirements from repository managers and DCAT about what kinds of reports they would like to see in a proposed content analysis module. It has been often requested, but almost no requirements have been stated so far."
  • DS- 824 (Jim Ottaviani, code review in process?): Request Copy function for XMLUI; would allow author of item to give viewing privs to restricted item
  • Any others?

 

 

Actions Items 

Action Item

Assignee

Deadline

1) Metadata project - prepping for review group

    • fix references to preliminary mappings on proposal page - make easier to find?
    • add link to OR13 preso on proposal page
    • clean up the preliminary DC mapping
Metadata team - Sarah P., Bram, Amy, Maureen 

2) Metadata project - research / brainstorm on recruiting

    • look at other applications using DC - Omeka uses unqualified DC, others?
    • think about / ask others about who could participate in review groups
ALL 
3) Contact metadata project volunteers to date to update them, ask for their feedback on review group ideaVal 
4) DS-1583 Adopt interface translating by Translatewiki.net - no responses from mailing list email or comments on JIRA, TWN integration php code still needs to be reviewed.Bram 

5) Re-start JIRA reviews

a) Everyone should select a JIRA issue of interest (Bram's recommended view: https://jira.duraspace.org/browse/DS#selectedTab=com.atlassian.jira.plugin.system.project%3Aissues-panel)

    • Received: help to judge whether the incoming tickets contain enough detail
    • More details needed: try to ask relevant questions in the comments, poking the original submitter to provide more detail
    • Volunteer needed: There are today 155 issues waiting for a volunteer. You can put some of these tickets in the spotlight by commenting or +1 on them to indicate that they are really important to you.

b) If the issue you select merits DCAT discussion (you want to confirm the importance of the request, want input on request, want to propose DCAT sending a msg to the listserve to find volunteers, etc.) please schedule the month for which you'd like to hold the discussion on the DCAT Discussion Schedule. If your JIRA issue doesn't merit a DCAT discussion, use JIRA to follow up directly.

c) Monthly discussion leaders should use the DCAT Discussion Forum to start your discussions with the rest of DCAT.

d) Post links/updates to the JIRA issue (summary of DCAT discussion with links to forum, etc.).

ALL