Uploaded image for project: 'DSpace'
  1. DSpace
  2. DS-1870

DSpaceMETSIngester is hard-coded to one profile, it should be generalised

    Details

    • Type: Improvement
    • Status: Volunteer Needed (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: SWORD
    • Attachments:
      0
    • Comments:
      3
    • Documentation Status:
      Needed

      Description

      Whilst SWORD (as a transport mechanism) and METS (as a Metadata Encoding Schema) are content-neutral, the ingester class within DSpace that handles METS packages has been hard-coded for one specific
      content-model.
      This makes is difficult to extend DSpace to ingest data used by other systems.

      It makes sense for the METS Ingester to read a configuration file to determine which profiles are acceptable, and then to select the appropriate XSLT Cross-Walker to map from <external supplier> into
      <repository schema>

      I am proposing this, as I am trying to create an importer to ingest a METS package that doesn't contain the "epdcx" data-payload as defined in the "DSpace METS SIP Profile" definition.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              ian.stuart Ian Stuart
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: