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

XOAI configuration/documentation

    Details

    • Attachments:
      0
    • Comments:
      1
    • Documentation Status:
      Needed

      Description

      While I was configuring DSpace 3.2 I stumbled about some config settings mentioned in the Docs and in the code but not present in the cfg files.

      I took a look at the configuration parameters in
      [dspace]/build.properties
      [dspace]/config/dspace.cfg
      [dspace]/config/modules/oai.cfg
      and the documentation and found the parameter

      dspace.oai.url

      mentioned in the Documentation https://wiki.duraspace.org/display/DSDOC3x/Configuration
      to be set in dspace.cfg
      and in https://wiki.duraspace.org/display/DSDOC3x/OAI
      to be set in oai.cfg
      but is not present in any of these.
      It is used in:
      [dspace-src]/dspace-api/src/main/java/org/dspace/content/crosswalk/OREDisseminationCrosswalk.java
      and
      [dspace-src]/dspace-xmlui/src/main/java/org/dspace/app/xmlui/aspect/administrative/ControlPanal.java

      Furthermore oai.cfg mentions dspace.oai.uri to be needed see

      1. The webapp responsible for minting the URIs for ORE Resource Maps.
      2. If using oai, the dspace.oai.uri config value must be set.
      3. The URIs generated for ORE ReMs follow the following convention for both cases.
      4. format: [baseURI]/metadata/handle/[theHandle]/ore.xml
      5. Default value is oai
        #ore.authoritative.source = oai
        which is not set anywhere and most like should be dspace.oai.url which is used in the OREDisseminationCrosswalk see above.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              cjuergen Claudia Jürgen
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: