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

Database 'info' / 'status' scripts should check for required groups/registries

    XMLWordPrintable

    Details

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

      Description

      Our ./dspace database status script is an excellent way to determine if your database schema is up-to-date, etc. But, it could be improved to also check for required content within that schema, especially the following:

      • Required groups (Anonymous and Administrator) exist
      • Required registries (esp. 'dc' and 'eperson' registries) exist. If there is also a way to check if registries are up-to-date, that'd be nice (but that may not be easy to implement, at least currently).

      These checks would help users to more easily validate installations/upgrades. Occasionally, we've hit scenarios where the database schemas are updated successfully, but group or registry updates (which are triggered as Flyway callbacks) later fail. These callback failures are only logged (in dspace.log), and the status script will report "success" (as Flyway does not validate that any callbacks also succeed).

      Resources:

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              tdonohue Tim Donohue
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated: