Opened 14 years ago

Closed 13 years ago

#497 closed feature (fixed)

Qualified DC in OAIserver

Reported by: kjdon Owned by: kjdon
Priority: moderate Milestone: CD-ROM Release for UNESCO
Component: Greenstone2 Runtime Severity: major
Keywords: Cc:


Enhance the OAI server to work with qualified dublin core.

  • Need to find or define a schema for qdc, as the OAI specification doesn't include one.
  • Make it an option to the server - currently we only support one metadata set I think, so need to make sure that we can add another one.
  • If we support qdc, does this mean it needs to be available for all sets (= collections)? Or can individual sets support different metadata sets?

Change History (4)

comment:1 by kjdon, 14 years ago

All collections that you want to serve using our oaiserver must provide a mapping to DC. If a collection happens to have qdc metadata, then make the server use that (if qdc was requested).

I assume that dc is a subset of qdc??

comment:2 by kjdon, 13 years ago

Owner: changed from nobody to kjdon
Status: newassigned

I have done most of this.

The new metadata set is called gsdl_qdc. It uses dc prefix for elements.

Still to do:

  • Restrict output to elements actually in the set. Need a list somewhere that names all the elements. For all sets.
  • Remove the qualified name from the element. eg CoverageSpatial should become spatial in the output.
  • mapping in oai.cfg - need to have separate mappings for dc and qdc. Since they use teh same element ns, we need to change the mapping rules to use teh set name instead.

ie oaimapping dls.Title oai_dc.title and modify the code accordingly.

comment:3 by kjdon, 13 years ago

This is all done now except the bit where we need to turn dc.Coverage hat Spatial into dc.spatial

comment:4 by kjdon, 13 years ago

Resolution: fixed
Status: assignedclosed

I have finished this now :-) Just needs other people to test.

Note: See TracTickets for help on using tickets.