Uploaded image for project: 'Fedora Repository Project'
  1. Fedora Repository Project
  2. FCREPO-3337

Refactor storage configuration

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: Fedora 6.0.0
    • Fix Version/s: Fedora 6.0.0
    • Component/s: f4-core
    • Labels:
      None

      Description

      Currently, F6 is using the following properties to define where it places OCFL related files on disk:

      private static final String OCFL_STAGING_DIR_KEY = "fcrepo.ocfl.staging.dir
      public static final String OCFL_STORAGE_ROOT_DIR_KEY = "fcrepo.ocfl.storage.root.dir";
      public static final String OCFL_WORK_DIR_KEY = "fcrepo.ocfl.work.dir";

      Additionally, the OCFL work directory is being incorrectly used to store files that are unrelated to the directory's purpose as a temp space that's used by the OCFL client.

      Ideally, this would be refactored to look something like the following:

      fcrepo/ <-- fcrepo.home: contains all F6 on disk data and config
      └── data/
      ├── ocfl-root/ <-- fcrepo.ocfl.storage: contains OCFL storage root
      ├── staging/ <-- fcrepo.ocfl.staging: contains files waiting to be moved into OCFL
      └── temp/ <-- fcrepo.temp: contains ocfl-java temp files and potentially other random files

      I can see a use case for having the OCFL storage root outside of fcrepo.home, but we may not even need the staging and temp locations to be configurable.

      It would be nice to just be able to do -Dfcrepo.home=target/fcrepo and have all of the various files written within the target directory rather than either having to deal with the default location in temp space or set a laundry list of properties.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              pwinckles Peter Winckles
              Reporter:
              pwinckles Peter Winckles
              Reviewer:
              Andrew Woods
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support