Difference between revisions of "Archivematica 1.12.0 and Storage Service 0.17.0 release notes"

From Archivematica
Jump to navigation Jump to search
(Add note on username database migration)
(One intermediate revision by one other user not shown)
Line 13: Line 13:
  
 
For development purposes, most of our developers prefer to use Docker containers. These and all above environments are linked from the installation instructions above.
 
For development purposes, most of our developers prefer to use Docker containers. These and all above environments are linked from the installation instructions above.
 +
 +
Please note due to a dependency issue we have not provided RPMs for the 1.12 release. We plan to address this issue in a point release and provide RPMs then.
  
 
<div style="padding: 10px 10px; border: 1px solid black; background-color: #F79086;">Note: if you are upgrading from Archivematica 1.10.x or earlier, please be sure to clean up the completed transfers watched directory before upgrading. Instructions can be found on the [https://www.archivematica.org/en/docs/archivematica-1.11/admin-manual/installation-setup/upgrading/upgrading/#upgrade Upgrading] page in the documentation. </div> <p>
 
<div style="padding: 10px 10px; border: 1px solid black; background-color: #F79086;">Note: if you are upgrading from Archivematica 1.10.x or earlier, please be sure to clean up the completed transfers watched directory before upgrading. Instructions can be found on the [https://www.archivematica.org/en/docs/archivematica-1.11/admin-manual/installation-setup/upgrading/upgrading/#upgrade Upgrading] page in the documentation. </div> <p>
Line 81: Line 83:
 
Archivematica has been upgraded to Django 1.12 LTS. Our next target is Django 2.2 LTS!
 
Archivematica has been upgraded to Django 1.12 LTS. Our next target is Django 2.2 LTS!
  
For a seamless experience for your users make sure that all active user sessions are deleted. We explain how here: [https://www.archivematica.org/en/docs/archivematica-1.12/admin-manual/maintenance/maintenance/#clear-user-sessions Maintenance > Clear user sessions].
+
There are a couple of things to be aware of during the Archivematica upgrade in this respect:
 +
* For a seamless experience for your users make sure that all active user sessions are deleted. We explain how here: [https://www.archivematica.org/en/docs/archivematica-1.12/admin-manual/maintenance/maintenance/#clear-user-sessions Maintenance > Clear user sessions].
 +
* Django's User model now comes with a character limit of 150 characters. In Archivematica v1.11.x or older we had that limit set to 250 characters via a third-party app that we have now deleted. During the database migration (i.e. when running manage.py migrate), users may be required to fix the problem manually. See the [https://github.com/artefactual/archivematica/blob/f87d2f39acce9a59bf49f72fd7e57f9eced2dbe5/src/dashboard/src/main/migrations/0078_username_check.py#L1-L20 migration module documentation] for more details. We expect this to be highly unlikely to happen since the exception is only triggered when the 150 character limit in the username field is exceeded.
  
 
=== Replace whitelist with allowlist ===
 
=== Replace whitelist with allowlist ===

Revision as of 10:47, 9 September 2020

Home > Release Notes > Archivematica 1.12.0 and Storage Service 0.17.0

Release date: still in progress!

Environments

Please see the installation instructions.

Archivematica 1.11 and Storage Service 0.16 have been tested in the following environments:

  • Ubuntu 18.04 64-bit Server Edition
  • CentOS 7 64-bit

For development purposes, most of our developers prefer to use Docker containers. These and all above environments are linked from the installation instructions above.

Please note due to a dependency issue we have not provided RPMs for the 1.12 release. We plan to address this issue in a point release and provide RPMs then.

Note: if you are upgrading from Archivematica 1.10.x or earlier, please be sure to clean up the completed transfers watched directory before upgrading. Instructions can be found on the Upgrading page in the documentation.

Added

Processing configuration selector

This feature allows the user to choose a processing configuration at the time of transfer by way of a drop down in the "Start transfer" button.

This feature has been sponsored by Simon Fraser University Archives. Thank you!

Column selectors for the Backlog and Archival Storage tab

Users can now choose the columns displayed while browsing the Backlog and Archival Storage tabs so they can see the information most relevant to them.

These features have been sponsored by Simon Fraser University Archives. Thank you!


AIP location column on Archival Storage tab

This feature has been sponsored by Picturae. Thank you!


Downloadable CSV from Archival Storage search

Users can now download a CSV containing all entries in Archival Storage, containing these columns: AIP name, Size, UUID, Number of files, Date stored, Status, Encrypted, and Storage Location

This feature has been sponsored by Picturae. Thank you!

Central Authorization Service (CAS) for Archivematica and Storage Service

This feature has been sponsored by Simon Fraser University Archives. Thank you!

OpenID Connect (OIDC) support for Archivematica and Storage Service

Experimental! Please share your feedback.

OIDC support is a community contribution by Wellcome Collection. Thank you!

Changed

Django 1.12 support

Archivematica has been upgraded to Django 1.12 LTS. Our next target is Django 2.2 LTS!

There are a couple of things to be aware of during the Archivematica upgrade in this respect:

  • For a seamless experience for your users make sure that all active user sessions are deleted. We explain how here: Maintenance > Clear user sessions.
  • Django's User model now comes with a character limit of 150 characters. In Archivematica v1.11.x or older we had that limit set to 250 characters via a third-party app that we have now deleted. During the database migration (i.e. when running manage.py migrate), users may be required to fix the problem manually. See the migration module documentation for more details. We expect this to be highly unlikely to happen since the exception is only triggered when the 150 character limit in the username field is exceeded.

Replace whitelist with allowlist

We have changed "whitelist" to "allowlist" in an effort to use more inclusive language throughout Archivematica's code.

Fixed

And more! Please see the 1.12 milestone in Github for all issues addressed in this release: https://github.com/archivematica/Issues/milestone/12