Fixes issue #407

• Changes the help text for the ManifestsRequired and ManifestsAllowed elements in the BagIt Profile form to reflect recent changes to these after we excluded md5 from the checksum algorithms.
• Shortens some help text in the BagIt Profile form.

Question: I think we should make Manifests Allowed required in the form? I could not figure out how to do that, so tips welcome.

Limits organizations to one BagIt Profile by changing database relationships. Makes a bunch of other updates throughout the app as a result of this change.

Note for reviewers: this is a pretty intensive PR, so please take the time to pull down the app and test things out locally to make sure it's all working as expected.

fixes #399

Adds a PageTitleMixin and implements it across the application. This means that all pages now have a meta page title which aligns with the h1 on the page. It also allowed me to get rid of some get_context_data blocks in views, which was a nice feeling.

Asking for a review on this because it's fairly invasive.

Fixes #473

Transfers should not be checked until they have been completely uploaded. For large transfers, a check is necessary to ensure the bag is not in the process of being transferred.

Checking while bags are still being transferred results in incorrect error messages and failure reports.

In alignments with efforts to reduce harmful and oppressive language in all aspects of the RAC's work, the default branch on this repository should be renamed from master to base.

1. Move to a new default branch and push:

git branch -m master base
git push -u origin base

2. Change default branch in GitHub.
3. Update any CI integrations (Travis CI/GitHub Actions) which rely on this branch.

Local clones can update refs as follows:

$ git checkout master
$ git branch -m master base
$ git fetch
$ git branch --unset-upstream
$ git branch -u origin/base
$ git symbolic-ref refs/remotes/origin/HEAD refs/remotes/origin/base

Is your feature request related to a problem? Please describe.

The original implementation of Aurora allowed organizations to have multiple BagIt Profiles. However, we so far don't have a use case for multiple Profiles associated with a single organization.

Having multiple BagIt Profiles associated with an organization also blocks us from doing some things which would improve validation, like dynamically fetching the BagIt Profile's URL from Aurora, rather than having to rely on hardcoded URLs.

Describe the solution you'd like

Remove the ForeignKey relationship on BagItProfiles to Organizations, and add a ForeignKey relationship from Organizations to BagIt Profiles. In BagIt Profile validation, fetch the BagIt Profile by using Django's reverse utility. Additional work will need to be done in Views, Templates and API Serializers to account for the above changes.

Describe alternatives you've considered

We could leave this as-is; it's not necessarily hurting anyone, but it's kind of annoying.

Adds models for metadata in bag-info.txt, as per #125. Started to add this data into views, but leaving most of that work for other PRs.

This is branched from #132, so that should be merged first.

Is your feature request related to a problem? Please describe.

See #539. For users not using AWS services, the password will need to be stored in the app database, while for Cognito implementations the password should be stored in Cognito.

Describe the solution you'd like

Clarify models and handling of auth so it works for both local and Cognito users.

Adds a script that can be run to easily add system users and groups (and associate users with the right groups) for Users and Organziations which already exist in Aurora's database. Useful when migrating to a new server.

Is your feature request related to a problem? Please describe.

When you scroll down with too many results, the top row goes away (under the transfer, appraise and accession pages) which result in scrolling back and forth a lot.

Describe the solution you'd like

Is there a way to freeze the top row or make it so that it moves in sync when scrolling.

Additional context

Feel free to disagree but I feel it kills a lot of time scrolling back and forth.

Is your feature request related to a problem? Please describe.

Both donor and archivist users have difficulty searching for/locating a specific transfer in Aurora. Donor users have added their external identifier to the bag title name to aid searching, and archivists are currently tracking specific transfers by metadata including title, record type, creator, and upload time. Search/ locating specific transfers can be improved by adding transfer ids to tables and detail views consistently across the app and in email notifications.

Describe the solution you'd like

Transfer page table (both All Transfers and My Transfers tabs)

• Add external identifier to "Name" column in the format: title (external identifier). If a bag is not valid, use the bag-it-name value instead.
• Add "Transfer File ID" column containing machine file id.
• Reformat "Dates "column to remove day: month year - month year to make more room in the table
• Change column order to: Name, Transfer File ID, Status, Dates, ...
• Rename "Upload Time" column to "Transfer Date" to match Appraisal Queue

Appraisal Queue

• Rename "Transfer File Name" column to "Transfer File ID" to match new column in Transfer page table. Table values should be the machine file id.

Organization Page (Recent Transfers table)

• Rename column "Bag Name" to "Name" to match Transfer page table
• Change value in name column to match Transfer page table: bag title (external identifier). If bag is not valid, use the bag-it-name value instead.
• Change "Upload Time" column name to be "Transfer Date" to match Transfer page table and Appraisal Queue table.

Accession Record (Transfers table)

• Rename "Name" column to be "Transfer File ID" to match other tables in Aurora. Table values should be the machine file id.

Transfer Details page

• Add the words "Details for" to the h1 ahead of the bag name to match the Appraisal Queue details modal.
• Add the machine file id as a <p> below the header if that value is available

Appraisal Details modal

• Change the modal to match the Transfer Details page, ie. use the bag-it-name as the title and add the machine file id below the title as seen in the screenshot in the previous section.

Email notification

• For transfers that pass validation, include the bag title and external identifier in the email text: The transfer [bag title (external identifier)] with the bag name [bag-it-name] was received at {} and has passed all automated validation checks:', 'You can view the current status of this transfer at {}'
• For transfers that fail validation, add additional text: An error occurred for the transfer with bag name {}

Dashboard

• Leave the Recent Transfers section links as the bag-it-name, since these are just quick links that do not need to be complicated with additional identifiers.

Describe alternatives you've considered

• We could use the transfer file id as the header in detail pages and on the Dashboard, but because invalid bags will not have this value, I'm suggesting sticking with the bag-it-name for consistency.
• There may be more explanatory text that could be added to the email notification for a failed bag since that notification cannot provide any metadata to help clarify which bag is invalid.

Additional context

Once changes are made, communicate to donor users that the external identifier does not need to be added as part of the title.

Is your feature request related to a problem? Please describe.

The transfer status on the Aurora /transfers page shows a progress bar and the exact status description. However, on the dashboard, each transfer status indication is binary with text indicating that it either passed or failed validation: Transfer by [user] passed/failed validation.

As we saw from bag 0c962a5a-0456-49c7-b7b1-58c1b24ce57c in a recent dev transfer, this can cause confusion for the user when the transfer status is "Transfer Completed" where the bag passed validation, but on the dashboard it says it failed validation.

Describe the solution you'd like

There are a few possibilities here. I think the idea of having this info on the dashboard is so that a user can quickly see if a bag was successfully transferred with no problems. We could adjust the text to have 3 options:

1. Transfer by [user] is in progress if the transfer has a status of "transfer started" or "transfer completed". No red or green color.
2. Transfer by [user] failed validation if the transfer has a status of invalid. Red color.
3. Transfer by [user] passed validation if the transfer has any other status. Green color.

Describe alternatives you've considered

1. We could also adjust the dashboard table to include the same transfer status column that is on the transfers page.
2. A simple approach would be to edit the text on the dashboard to match the transfer status on the transfers page: Transfer by [user]. Status: [transfer status]

Additional context

There are currently 9 possible statuses in Aurora:

• Transfer Started
• Transfer Complete
• Invalid
• Validated
• Rejected
• Accepted
• Accessioning Started
• In Accession Queue
• Accession Complete

Is your feature request related to a problem? Please describe.

Bag metadata date fields use Django datetime fields. This is confusing for end users.

Describe the solution you'd like

Convert datetime fields to date fields.

Additional context

Will need to investigate how this impacts existing data.