AtoM wiki - User contributions [en]

Community/Groups/NA

2024-05-16T17:25:06Z

JennR:

{{#pagetitle: Joint US Canada Users group}}
[[Main Page]] > [[Community]] > [[Community/Groups]] > Community/Groups/NA

'''Background'''

The Joint US-Canada AtoM Users Group began in 2020. We discuss issues of interest identified in surveys carried out of group members. To date, we have 100 members on our mailing list from the US, Canada, and a small number from Europe. Originally, we held quarterly meetings, but now we meet twice yearly using Zoom. We also have a subgroup, the New Users Group, which makes training videos for our YouTube channel. We also have a subgroup, the New Users Group, which makes training videos for our YouTube channel.

'''Who is it for?'''

Membership is open to anyone who is interested.

'''Contact'''
To join, send an email with your name, institution, and email address to mkosta (at) uwo (dot) ca. Indicate whether you are willing to share your contact information with other Users Group members. You will then be added to the mailing list.

'''Past presentations include'''

November 2023: Presentations on how we use AtoM with:
Sr. Rebecca Abel, Sisters of St. Benedict, Indiana, John Thiesen, Bethel College, Kansas, Stephen Logsdon, Bernard Becker Medical Library, Washington University School of Medicine, Missouri, Sandra Yates, McGovern Historical Research Center, Texas Medical Center Library, Texas

November 2023: AtoM Foundation Update with:
Anna Dysert, McGill University, Quebec

March 2023: Social Networks and Archival Context (SNAC) with:
Dina Herbert and Jerry Simmons of NARA

March 2023: National Finding Aid Network (NAFAN) with:
Adrian Turner of the California Digital Library.

January 2023: AtoM Import Tool for Formatting Bulk Descriptions at Simon Fraser University Archives with:
Kelsey Poloney

October 2022: IIIF and digital images in AtoM with:
Kelli Babcock, The University of Toronto

October 2022: Archives Canada with:
Joanna Aiton-Kerr and Yves Lapointe, Canada Council of Archives

June 2022 Using metadata from AtoM in Wikidata with:
Anna Dysert, McGill University

March 2022 AtoM Foundation Update with:
Brett Lougheed, Anna McNally, Cliff Hight

September 2021 CAAIS Study with:
Melissa McCarthy, Archivist, City of Edmonton, Edmonton, Alberta

May 2021 Bulk Uploads with CSV with:
Jody Robinson, Archivist of the Eastern Townships Resource Centre, Bishops University. Sherbrooke, Québec

Community/Groups/NA

2023-12-02T01:49:51Z

JennR:

{{#pagetitle: Joint US Canada Users group}}
[[Main Page]] > [[Community]] > [[Community/Groups]] > Community/Groups/NA

'''Background'''

The Joint US-Canada AtoM Users Group began in 2020. We discuss issues of interest identified in surveys carried out of group members. To date, we have 100 members on our mailing list from the US, Canada, and a small number from Europe. Originally, we held quarterly meetings, but now we meet twice yearly using Zoom. We also have a subgroup, the New Users Group, which makes training videos for our YouTube channel. We also have a subgroup, the New Users Group, which makes training videos for our YouTube channel.

'''Who is it for?'''

Membership is open to anyone who is interested.

'''Contact'''
To join, send an email with your name, institution, and email address to csjarchives (at) csjcanada (dot) org. Indicate whether you are willing to share your contact information with other Users Group members. You will then be added to the mailing list.

'''Past presentations include'''

November 2023: Presentations on how we use AtoM with:
Sr. Rebecca Abel, Sisters of St. Benedict, Indiana, John Thiesen, Bethel College, Kansas, Stephen Logsdon, Bernard Becker Medical Library, Washington University School of Medicine, Missouri, Sandra Yates, McGovern Historical Research Center, Texas Medical Center Library, Texas

November 2023: AtoM Foundation Update with:
Anna Dysert, McGill University, Quebec

March 2023: Social Networks and Archival Context (SNAC) with:
Dina Herbert and Jerry Simmons of NARA

March 2023: National Finding Aid Network (NAFAN) with:
Adrian Turner of the California Digital Library.

January 2023: AtoM Import Tool for Formatting Bulk Descriptions at Simon Fraser University Archives with:
Kelsey Poloney

October 2022: IIIF and digital images in AtoM with:
Kelli Babcock, The University of Toronto

October 2022: Archives Canada with:
Joanna Aiton-Kerr and Yves Lapointe, Canada Council of Archives

June 2022 Using metadata from AtoM in Wikidata with:
Anna Dysert, McGill University

March 2022 AtoM Foundation Update with:
Brett Lougheed, Anna McNally, Cliff Hight

September 2021 CAAIS Study with:
Melissa McCarthy, Archivist, City of Edmonton, Edmonton, Alberta

May 2021 Bulk Uploads with CSV with:
Jody Robinson, Archivist of the Eastern Townships Resource Centre, Bishops University. Sherbrooke, Québec

Community/Groups/NA

2023-12-02T01:47:44Z

JennR:

[https://wiki.accesstomemory.org/wiki/Community/Groups Main Page > Community > Community/Groups]> Community/Groups/NA

'''Background'''

The Joint US-Canada AtoM Users Group began in 2020. We discuss issues of interest identified in surveys carried out of group members. To date, we have 100 members on our mailing list from the US, Canada, and a small number from Europe. Originally, we held quarterly meetings, but now we meet twice yearly using Zoom. We also have a subgroup, the New Users Group, which makes training videos for our YouTube channel. We also have a subgroup, the New Users Group, which makes training videos for our YouTube channel.

'''Who is it for?'''

Membership is open to anyone who is interested.

'''Contact'''
To join, send an email with your name, institution, and email address to csjarchives (at) csjcanada (dot) org. Indicate whether you are willing to share your contact information with other Users Group members. You will then be added to the mailing list.

'''Past presentations include'''

November 2023: Presentations on how we use AtoM with:
Sr. Rebecca Abel, Sisters of St. Benedict, Indiana, John Thiesen, Bethel College, Kansas, Stephen Logsdon, Bernard Becker Medical Library, Washington University School of Medicine, Missouri, Sandra Yates, McGovern Historical Research Center, Texas Medical Center Library, Texas

November 2023: AtoM Foundation Update with:
Anna Dysert, McGill University, Quebec

March 2023: Social Networks and Archival Context (SNAC) with:
Dina Herbert and Jerry Simmons of NARA

March 2023: National Finding Aid Network (NAFAN) with:
Adrian Turner of the California Digital Library.

January 2023: AtoM Import Tool for Formatting Bulk Descriptions at Simon Fraser University Archives with:
Kelsey Poloney

October 2022: IIIF and digital images in AtoM with:
Kelli Babcock, The University of Toronto

October 2022: Archives Canada with:
Joanna Aiton-Kerr and Yves Lapointe, Canada Council of Archives

June 2022 Using metadata from AtoM in Wikidata with:
Anna Dysert, McGill University

March 2022 AtoM Foundation Update with:
Brett Lougheed, Anna McNally, Cliff Hight

September 2021 CAAIS Study with:
Melissa McCarthy, Archivist, City of Edmonton, Edmonton, Alberta

May 2021 Bulk Uploads with CSV with:
Jody Robinson, Archivist of the Eastern Townships Resource Centre, Bishops University. Sherbrooke, Québec

Community/Groups/NA

2023-12-02T01:46:10Z

JennR:

Main Page > Community > Community/Groups > Community/Groups/NA

'''Background'''

The Joint US-Canada AtoM Users Group began in 2020. We discuss issues of interest identified in surveys carried out of group members. To date, we have 100 members on our mailing list from the US, Canada, and a small number from Europe. Originally, we held quarterly meetings, but now we meet twice yearly using Zoom. We also have a subgroup, the New Users Group, which makes training videos for our YouTube channel. We also have a subgroup, the New Users Group, which makes training videos for our YouTube channel.

'''Who is it for?'''

Membership is open to anyone who is interested.

'''Contact'''
To join, send an email with your name, institution, and email address to csjarchives (at) csjcanada (dot) org. Indicate whether you are willing to share your contact information with other Users Group members. You will then be added to the mailing list.

'''Past presentations include'''

November 2023: Presentations on how we use AtoM with:
Sr. Rebecca Abel, Sisters of St. Benedict, Indiana, John Thiesen, Bethel College, Kansas, Stephen Logsdon, Bernard Becker Medical Library, Washington University School of Medicine, Missouri, Sandra Yates, McGovern Historical Research Center, Texas Medical Center Library, Texas

November 2023: AtoM Foundation Update with:
Anna Dysert, McGill University, Quebec

March 2023: Social Networks and Archival Context (SNAC) with:
Dina Herbert and Jerry Simmons of NARA

March 2023: National Finding Aid Network (NAFAN) with:
Adrian Turner of the California Digital Library.

January 2023: AtoM Import Tool for Formatting Bulk Descriptions at Simon Fraser University Archives with:
Kelsey Poloney

October 2022: IIIF and digital images in AtoM with:
Kelli Babcock, The University of Toronto

October 2022: Archives Canada with:
Joanna Aiton-Kerr and Yves Lapointe, Canada Council of Archives

June 2022 Using metadata from AtoM in Wikidata with:
Anna Dysert, McGill University

March 2022 AtoM Foundation Update with:
Brett Lougheed, Anna McNally, Cliff Hight

September 2021 CAAIS Study with:
Melissa McCarthy, Archivist, City of Edmonton, Edmonton, Alberta

May 2021 Bulk Uploads with CSV with:
Jody Robinson, Archivist of the Eastern Townships Resource Centre, Bishops University. Sherbrooke, Québec

Community/Groups/NA

2023-12-02T01:45:41Z

JennR:

'''Background'''

The Joint US-Canada AtoM Users Group began in 2020. We discuss issues of interest identified in surveys carried out of group members. To date, we have 100 members on our mailing list from the US, Canada, and a small number from Europe. Originally, we held quarterly meetings, but now we meet twice yearly using Zoom. We also have a subgroup, the New Users Group, which makes training videos for our YouTube channel. We also have a subgroup, the New Users Group, which makes training videos for our YouTube channel.

'''Who is it for?'''

Membership is open to anyone who is interested.

'''Contact'''
To join, send an email with your name, institution, and email address to csjarchives (at) csjcanada (dot) org. Indicate whether you are willing to share your contact information with other Users Group members. You will then be added to the mailing list.

'''Past presentations include'''

November 2023: Presentations on how we use AtoM with:
Sr. Rebecca Abel, Sisters of St. Benedict, Indiana, John Thiesen, Bethel College, Kansas, Stephen Logsdon, Bernard Becker Medical Library, Washington University School of Medicine, Missouri, Sandra Yates, McGovern Historical Research Center, Texas Medical Center Library, Texas

November 2023: AtoM Foundation Update with:
Anna Dysert, McGill University, Quebec

March 2023: Social Networks and Archival Context (SNAC) with:
Dina Herbert and Jerry Simmons of NARA

March 2023: National Finding Aid Network (NAFAN) with:
Adrian Turner of the California Digital Library.

January 2023: AtoM Import Tool for Formatting Bulk Descriptions at Simon Fraser University Archives with:
Kelsey Poloney

October 2022: IIIF and digital images in AtoM with:
Kelli Babcock, The University of Toronto

October 2022: Archives Canada with:
Joanna Aiton-Kerr and Yves Lapointe, Canada Council of Archives

June 2022 Using metadata from AtoM in Wikidata with:
Anna Dysert, McGill University

March 2022 AtoM Foundation Update with:
Brett Lougheed, Anna McNally, Cliff Hight

September 2021 CAAIS Study with:
Melissa McCarthy, Archivist, City of Edmonton, Edmonton, Alberta

May 2021 Bulk Uploads with CSV with:
Jody Robinson, Archivist of the Eastern Townships Resource Centre, Bishops University. Sherbrooke, Québec

Community/Groups/NA

2023-12-02T01:39:36Z

JennR: Created page with "The Joint US-Canada AtoM Users Group began in 2020. We discuss issues of interest identified in surveys carried out of group members. To date, we have 100 members on our maili..."

The Joint US-Canada AtoM Users Group began in 2020. We discuss issues of interest identified in surveys carried out of group members. To date, we have 100 members on our mailing list from the US, Canada, and a small number from Europe.

Originally, we held quarterly meetings, but now we meet twice yearly using Zoom. Membership is open to anyone who is interested. To join, send an email with your name, institution, and email address to csjarchives (at) csjcanada (dot) org. Indicate whether you are willing to share your contact information with other Users Group members. You will then be added to the mailing list.

We also have a subgroup, the New Users Group, which makes training videos for our YouTube channel.

Community/Groups

2023-12-02T01:38:50Z

JennR:

{{#pagetitle:Regional user groups}}
[[Main Page]] > [[Community]] > Community/Groups

This page holds information on local groups organized by AtoM users, including mandates, meeting times, resources, and more.

'''Current groups'''

* [[Community/Group/Australasia|Australiasia User group]]
* [[Community/Groups/Brazil|Brazil User group]]
* [[Community/Groups/Portugal|Portugal User group]]
* [[Community/Groups/SouthAfrica|South Africa User group]]
* [[Community/Groups/UK|UK User group]]
* [[Community/Groups/Midwest|Midwest User group]]
* [[Community/Groups/Sweden | Swedish User group]]
* [[Community/Groups/NA | Joint US Canada User group]]

<admonition type="tip">
Are you considering starting a User group in your region? Let us know about it! Feel free to leave a message in the AtoM [https://groups.google.com/forum/#!forum/ica-atom-users User forum]!
</admonition>

-----

* [[Community|Back to Community]]
* [[Main Page|AtoM wiki home]]

[[Category:Community]]

Releases/Release announcements/Release 2.7

2022-12-21T21:11:16Z

JennR: /* Command-line tasks */

{{#pagetitle:Release 2.7}}
[[Main Page]] > [[Releases]] > [[Releases/Release announcements]] > Release 2.7

'''Release date''': December 21, 2022

'''Download link''': [https://storage.accesstomemory.org/releases/atom-2.7.0.tar.gz atom-2.7.0.tar.gz]

'''Database schema version''': v192

'''Release 2.7''' is the first major AtoM release since July 2020, and includes new features, some dependency upgrades, accessibility improvements, as well as bug fixes. Some highlights include:

* An updated version of Bootstrap - both BS5 and BS2 are supported in 2.7
* The ability to use Central Authentication Service (CAS) for single sign on
* Enhanced Archivematica integration with the ability to download AIP and preservation files directly from AtoM
* Improved digital object metadata display area
* Introduction of a validation tool for CSV imports via the user interface
* New command line tasks to help verify imports and resolve issues

----
We’ve closed a number of issues as part of this release – you can view more details on each ticket in our issue tracker at the following links

* [https://projects.artefactual.com/versions/132 Release Overview]
* [https://bit.ly/3Wxus5e 2.7 issues]

----

Visit the [https://www.accesstomemory.org/download/ Downloads] page to download the most recent release, and consult the 2.7 [https://www.accesstomemory.org/docs/2.7/admin-manual/installation/upgrading/ Upgrading] and [https://www.accesstomemory.org/en/docs/2.7/admin-manual/installation/ Installation] guides in our documentation for further information.

If you’re a brand new AtoM user, we suggest that you deploy a new install with BS5. If you are performing an upgrade and you have a custom theme we recommend you continue to use BS2 at this time.

An overview of some of the major changes in the 2.7 release is included below, followed by a list of links to relevant tickets, sponsors and contributors, and documentation for new features.

<admonition type="tip">
Issue numbers associated with new features and bug fixes listed below refer to the AtoM project issue tracker. Artefactual uses the issue tracker to track development tasks, feature requirements, quality assurance testing, and related development discussion. You can use the numbers to search for the related issue ticket in our Issue tracker - often the tickets will include more information on how the feature was implemented.

For more information, see: [[Resources/Issue_tracker|Issue tracker]]
</admonition>

__TOC__

-----

===Accessibility===

Community contributor [https://github.com/mInnes-archives Matt Innes] has contributed a number of minor accessibility enhancements to the latest AtoM release, addressing elements such as adding missing aria labels or instructions, better tab navigation flow and general page structure improvements, removal of redundant elements affecting accessibility, etc. These changes do not affect the look or feel of AtoM, but should provide some quality of life improvements for users with assistive technologies such as screen readers.

''Community contributions from Matt Innes''

* #13535 - Enhance accessibility support of various AtoM template elements

====Bootstrap 5====

AtoM will be integrating Bootstrap 5 into AtoM. Bootstrap is a framework for developing websites and is used in AtoM to provide theme templates to administrators
This updated version of Bootstrap provides a number of improvements such as better security, responsiveness and accessibility.

The new version of Bootstrap enables significant accessibility and responsiveness improvements over previous AtoM versions and it has better responsiveness for public users accommodating portable devices with varying screen sizes making the websites more easily accessible independent of device.

The new version of Bootstrap will be available in future releases of AtoM and more information will be provided in future forum announcements.

'''Related documentation'''
* [https://accesstomemory.org/docs/2.7/user-manual/administer/themes/#themes Themes]

===Accessions===

This release sees some additional incremental support for elements of the Canadian Archival Accession Information Standard ([http://archivescanada.ca/CWG_AccessionStandard CAAIS]). In this release, we have added a basic module for managing events in conformance with CAAIS Element [http://archivescanada.ca/CWG_AccessionStandard#5.1_e 5.1], which are "the actions taken by repository staff throughout the accession process." The 5.1.1 Event Type field is linked to a new Accession Events taxonomy that can be customized by an administrator as needed.

''General bug fixes and enhancements''

* #13466 - Accession donors are not indexed properly

''Sponsored by the Government of the Northwest Territories''

* #13315 - Add ability to associate events with accession records

'''Related documentation''':

* [https://www.accesstomemory.org/docs/2.7/user-manual/add-edit-content/accessions/#add-accession-events Add events to an accession record]

===Authentication===

AtoM now supports use of the Central Authentication Service ([https://apereo.github.io/cas/4.2.x/protocol/CAS-Protocol-Specification.html CAS]) protocol for single sign-on and authentication management. Additionally, the previously undocumented support for LDAP now has configuration instructions in the Administrator's manual (on the same page as the CAS documentation linked below).

''Sponsored by Simon Fraser University Archives''

* #13383 - Support CAS single sign-on

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/admin-manual/customization/authentication/#cas-enabling Enable CAS authentication]

===Archivematica integration===

For users who are using AtoM with [https://www.archivematica.org Archivematica], administrators who have Archivematica access can now download AIP and preservation files directly from AtoM. This coincides with the digital object metadata improvements described in the [[Releases/Roadmap#Digital_objects|Digital objects]] section below.

''Sponsored by Simon Fraser University Archives''

* #13351 - Support AIP download from AtoM UI for authorized users

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/upload-digital-object/#digital-object-metadata-for-preservation-files Digital object metadata for preservation files]

===Authority records===

This release adds a minor enhancement that will provide a warning notification to authenticated users when a duplicate authority record identifier is entered. This warning is never shown to public users, similar to existing warnings in the standards-based templates.

''Sponsored by an undisclosed institution''

* #13373 - Display warning for duplicate authority record identifiers

===Command-line tasks===

In addition to the CLI enhancements described in the Import/Export section below, this release also includes a new task to help system administrators remove temporary files, such as old saved clipboards and downloads found in the jobs subdirectory. When troubleshooting upgrade issues related to the database schema version, users an also use a new option on the <code>tools:upgrade</code> task to run individual schema migrations, in case one is missed during an upgrade process.

Another feature that has been added as part of this release is replacing the AtoM web installer with a command line driver installation. This feature addresses the installation timeout via the web browser by moving the AtoM installation steps. It should simplify the installation process overall, better support automated deployments, and resolve the timeout issues resulting from the web installer's current use.

''General bug fixes and enhancements''

* #13368 - Add CLI option to migration task to run individual migrations
* #13440 - Add ability for tools:expire-data to delete temp files
* #13452 - Replace AtoM's web installer with a command-line driven installation process
* #13500 - Add CLI task to generate finding aids

''Sponsored by Mills Archive''

* #13361 - Add option to cache XML task to generate only EAD or DC XML

'''Related documentation'''

* [https://www.accesstomemory.org/en/docs/2.7/admin-manual/maintenance/cli-tools/#delete-temporary-data-saved-clipboards-access-log-and-downloads Expire data CLI task]
* [https://www.accesstomemory.org/docs/2.7/admin-manual/maintenance/cli-tools/#generate-and-cache-xml-for-all-archival-descriptions Cache XML CLI task]
* [https://www.accesstomemory.org/docs/2.7/admin-manual/maintenance/cli-tools/#generate-a-finding-aid Generate a finding aid CLI task]

===Digital objects===

The 2.7 release includes a number of minor enhancements to the Digital object functionality in AtoM. The Digital object metadata area has been expanded to display separate details about the original and all derivatives, and the corresponding public visibility controls in the Visible Elements module have also been expanded to match. Administrators can now enable an option that will allow public users to include digital objects in their clipboard downloads. A new API endpoint has been added to allow authorized users to access the master digital object associated with a description. Additionally, thanks to a community pull request, subtitle and chapter tracks can now be uploaded alongside audio and video digital objects.

''General bug fixes and enhancements''

* #13497 - Video derivatives not generated when linking via URL

''Community pull requests from Matt Innes''

* #13459 - Reintroduce responsive audio/video
* #13471 - Clarify digital object derivative settings
* #13490 - Add support for subtitle and chapter tracks in video and audio digital objects

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/upload-digital-object/#add-subtitle-caption-and-or-chapter-files-to-audio-and-video Add subtitle, caption, or chapter tracks to video and audio uploads]

''Sponsored by an undisclosed institution''

* #13395 - Add option to include digital objects in clipboard exports

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/export-xml/#including-digital-objects-with-an-xml-clipboard-export Including digital objects with an XML clipboard export]
* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/csv-export/#including-digital-objects-in-a-clipboard-csv-export Including digital objects with a CSV clipboard export]
* [https://www.accesstomemory.org/docs/2.7/user-manual/administer/settings/#clipboard-do-export-setting Enable Clipboard digital object export functionality]

''Sponsored by Simon Fraser University Library''

* #13388 - Improve digital object metadata display
* #13417 - Digital object preservation copy displays UCT time stamps

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/upload-digital-object/#digital-object-metadata Digital object metadata]
* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/upload-digital-object/#digital-object-metadata-for-preservation-files Digital object metadata for preservation files]
* [https://www.accesstomemory.org/docs/2.7/user-manual/add-edit-content/rights/#configure-a-preservation-system-access-statement Configure a preservation system access statement]

''Sponsored by the Mills Archive''

* #13436 - Add API endpoint to download master digital object

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/dev-manual/api/download-do/ Download digital object API endpoint]

===Finding aids and reports===

We've addressed a few issues that prevented finding aids from generating when the Library of Congress EAD DTD was inaccessible by using a local DTD instead, and added a new administrative setting that can disable finding aid generation. When disabled, related finding view page links and advanced search filters will also be hidden in the user interface.

''General bug fixes and enhancements''

* #13247 - Finding aid generation sometimes fails reading DTD file
* #13590 - Finding aid generation fails due to a "403 Forbidden" error
* #13593 - Add the ability to turn off finding aid features in the AtoM UI

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/reports-printing/print-finding-aid/#finding-aid-settings Finding aid settings]

===Import and export===

The 2.7 release includes a new major module to support better CSV imports - the ability to validate a CSV prior to import, from the command-line or via the user interface. Additionally, an administrator can set validation to run automatically before any import if desired. We've also added a few command-line tasks to help verify imports or resolve issues - one task can audit a CSV against AtoM's database and report any rows that were not imported, and another task can delete descriptions created by a CSV import for cases where the import results were not as expected.

Other bug fixes in this release include the ability to export in CSV RAD note types for cast, credit, and signatures as well as the ability to export descriptions in CSV from the clipboard in RAD.

''General bug fixes and enhancements''

* #13287 - Repository CSV import fails when new terms added to Description Statuses in import file
* #13295 - Authority record CSV import fails when encountering new entity type (or variations in capitalization)
* #13457 - Create command line task to delete records created by a CSV import
* #13475 - Enhance AtoM's csv:check-import task to support pre-import validation
* #13481 - Some RAD notes fields don't appear in CSV exports
* #13483 - Description CSV exports from clipboard only exporting in ISAD
* #13561 - Add ability to use CSV check task on a directory full of CSV files
* #13567 - CSV authority record import requires identifier column be populated
* #13569 - Add CSV audit import task

''The development of this tool has been made possible by the Council of Nova Scotia Archives and the Library and Archives Canada's Documentary Heritage Communities Programs''

* #13508 - Integrate AtoM's CSV Validator into the Web UI

''Sponsored by UN Geneva Library''

* #13549 - Add slug column to CSV information object export

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/csv-validation/ CSV validation]
* [https://www.accesstomemory.org/docs/2.7/admin-manual/maintenance/cli-import-export/#delete-csv-io-import-cli Delete descriptions created by a CSV import from the command-line]
* [https://www.accesstomemory.org/docs/2.7/admin-manual/maintenance/cli-import-export/#audit-io-csv-import-cli Audit a CSV import]

===Rights===

It's now possible to enable the Copyright pop-up to apply to all digital objects in AtoM, without needing to individually apply Rights statements to each related record for the pop-up to trigger.

''Sponsored by the UN Archives Geneva''

* #13570 - Add ability to apply copyright pop-up globally without accompanying Rights statement

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/add-edit-content/rights/#copyright-pop-up Add a copyright statement]

===Scalability and performance===

''General bug fixes and enhancements''

* #13435 - Permission denied creating a new child description when Grant "create" on parent
* #13437 - Digital object authorization code is too complicated

''Sponsored by an undisclosed institution''

* #11556 - Make AtoM's clipboard work with the Varnish Cache web application accelerator
* #13389 - Support ability for reverse proxies like Varnish to cache content that's not in the default culture
* #13415 - An archival description with many descendants loads slowly when the DO carousel is enabled

===Settings===

''Sponsored by an undisclosed institution''

* #13411 - Add setting to enable or disable repository "upload limit" widget

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/administer/settings/#archival-institution-upload-limits Archival institution upload limits]

===Treeview===

''General bug fixes and enhancements''

* #13423 - Full-width treeview fails to load for descriptions with 900K+ children
* #13446 - Clicking on a description in the full-width treeview doesn't update the page URL
* #13491 - Terms treeview list tab's "Next" pager button does not work

===Other bug fixes and enhancements===

* #12628 - Drag and drop on full-width treeview makes it difficult for public users to scroll on mobile devices
* #13297 - Privacy policy static page cannot be deleted from the menus
* #13458 - PDF logo not included in PDF Finding Aids
* #13469 - Do not return 404 responses from search/autocomplete when there are no results
* #13506 - Copyright pop-up preview page no longer renders preview content
* #13586 - Certain special characters displays incorrectly in Web Page Title

''Community code contributions from Matt Innes''

* #10682 - Cannot create new authority record and add relationship at the same time
* #13218 - Error when adding function related to another
* #13499 - Various relation dialog fixes and improvements
* #13515 - Capitalize initial letter of languages in menu
* #13544 - Exclude narrower terms link and filter tag always link to description results

''Community code contribution from Jason Hildebrand and PeaceWorks Technology Solutions''

* #13441 - Improve Dockerfile layers caching

Releases/Release announcements/Release 2.7

2022-12-21T21:09:24Z

JennR:

{{#pagetitle:Release 2.7}}
[[Main Page]] > [[Releases]] > [[Releases/Release announcements]] > Release 2.7

'''Release date''': December 21, 2022

'''Download link''': [https://storage.accesstomemory.org/releases/atom-2.7.0.tar.gz atom-2.7.0.tar.gz]

'''Database schema version''': v192

'''Release 2.7''' is the first major AtoM release since July 2020, and includes new features, some dependency upgrades, accessibility improvements, as well as bug fixes. Some highlights include:

* An updated version of Bootstrap - both BS5 and BS2 are supported in 2.7
* The ability to use Central Authentication Service (CAS) for single sign on
* Enhanced Archivematica integration with the ability to download AIP and preservation files directly from AtoM
* Improved digital object metadata display area
* Introduction of a validation tool for CSV imports via the user interface
* New command line tasks to help verify imports and resolve issues

----
We’ve closed a number of issues as part of this release – you can view more details on each ticket in our issue tracker at the following links

* [https://projects.artefactual.com/versions/132 Release Overview]
* [https://bit.ly/3Wxus5e 2.7 issues]

----

Visit the [https://www.accesstomemory.org/download/ Downloads] page to download the most recent release, and consult the 2.7 [https://www.accesstomemory.org/docs/2.7/admin-manual/installation/upgrading/ Upgrading] and [https://www.accesstomemory.org/en/docs/2.7/admin-manual/installation/ Installation] guides in our documentation for further information.

If you’re a brand new AtoM user, we suggest that you deploy a new install with BS5. If you are performing an upgrade and you have a custom theme we recommend you continue to use BS2 at this time.

An overview of some of the major changes in the 2.7 release is included below, followed by a list of links to relevant tickets, sponsors and contributors, and documentation for new features.

<admonition type="tip">
Issue numbers associated with new features and bug fixes listed below refer to the AtoM project issue tracker. Artefactual uses the issue tracker to track development tasks, feature requirements, quality assurance testing, and related development discussion. You can use the numbers to search for the related issue ticket in our Issue tracker - often the tickets will include more information on how the feature was implemented.

For more information, see: [[Resources/Issue_tracker|Issue tracker]]
</admonition>

__TOC__

-----

===Accessibility===

Community contributor [https://github.com/mInnes-archives Matt Innes] has contributed a number of minor accessibility enhancements to the latest AtoM release, addressing elements such as adding missing aria labels or instructions, better tab navigation flow and general page structure improvements, removal of redundant elements affecting accessibility, etc. These changes do not affect the look or feel of AtoM, but should provide some quality of life improvements for users with assistive technologies such as screen readers.

''Community contributions from Matt Innes''

* #13535 - Enhance accessibility support of various AtoM template elements

====Bootstrap 5====

AtoM will be integrating Bootstrap 5 into AtoM. Bootstrap is a framework for developing websites and is used in AtoM to provide theme templates to administrators
This updated version of Bootstrap provides a number of improvements such as better security, responsiveness and accessibility.

The new version of Bootstrap enables significant accessibility and responsiveness improvements over previous AtoM versions and it has better responsiveness for public users accommodating portable devices with varying screen sizes making the websites more easily accessible independent of device.

The new version of Bootstrap will be available in future releases of AtoM and more information will be provided in future forum announcements.

'''Related documentation'''
* [https://accesstomemory.org/docs/2.7/user-manual/administer/themes/#themes Themes]

===Accessions===

This release sees some additional incremental support for elements of the Canadian Archival Accession Information Standard ([http://archivescanada.ca/CWG_AccessionStandard CAAIS]). In this release, we have added a basic module for managing events in conformance with CAAIS Element [http://archivescanada.ca/CWG_AccessionStandard#5.1_e 5.1], which are "the actions taken by repository staff throughout the accession process." The 5.1.1 Event Type field is linked to a new Accession Events taxonomy that can be customized by an administrator as needed.

''General bug fixes and enhancements''

* #13466 - Accession donors are not indexed properly

''Sponsored by the Government of the Northwest Territories''

* #13315 - Add ability to associate events with accession records

'''Related documentation''':

* [https://www.accesstomemory.org/docs/2.7/user-manual/add-edit-content/accessions/#add-accession-events Add events to an accession record]

===Authentication===

AtoM now supports use of the Central Authentication Service ([https://apereo.github.io/cas/4.2.x/protocol/CAS-Protocol-Specification.html CAS]) protocol for single sign-on and authentication management. Additionally, the previously undocumented support for LDAP now has configuration instructions in the Administrator's manual (on the same page as the CAS documentation linked below).

''Sponsored by Simon Fraser University Archives''

* #13383 - Support CAS single sign-on

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/admin-manual/customization/authentication/#cas-enabling Enable CAS authentication]

===Archivematica integration===

For users who are using AtoM with [https://www.archivematica.org Archivematica], administrators who have Archivematica access can now download AIP and preservation files directly from AtoM. This coincides with the digital object metadata improvements described in the [[Releases/Roadmap#Digital_objects|Digital objects]] section below.

''Sponsored by Simon Fraser University Archives''

* #13351 - Support AIP download from AtoM UI for authorized users

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/upload-digital-object/#digital-object-metadata-for-preservation-files Digital object metadata for preservation files]

===Authority records===

This release adds a minor enhancement that will provide a warning notification to authenticated users when a duplicate authority record identifier is entered. This warning is never shown to public users, similar to existing warnings in the standards-based templates.

''Sponsored by an undisclosed institution''

* #13373 - Display warning for duplicate authority record identifiers

===Command-line tasks===

In addition to the CLI enhancements described in the Import/Export section below, this release also includes a new task to help system administrators remove temporary files, such as old saved clipboards and downloads found in the jobs subdirectory. When troubleshooting upgrade issues related to the database schema version, users an also use a new option on the <code>tools:upgrade</code> task to run individual schema migrations, in case one is missed during an upgrade process.

Another feature that has been added as part of this release is replacing the AtoM web installer with a command line driver installation. This feature addresses the installation timeout via the web browser by moving the AtoM installation steps. It should simplify the installation process overall, better support automated deployments, and resolve the timeout issues resulting from the web installer's current use.

''General bug fixes and enhancements''

* #13368 - Add CLI option to migration task to run individual migrations
* #13440 - Add ability for tools:expire-data to delete temp files
* #13452 - Replace AtoM's web installer with a command-line driven installation process
* #13500 - Add CLI task to generate finding aids

''Sponsored by Mills Archive''

* #13361 - Add option to cache XML task to generate only EAD or DC XML

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/admin-manual/maintenance/cli-tools/#delete-temporary-data-saved-clipboards-and-downloads Expire data CLI task]
* [https://www.accesstomemory.org/docs/2.7/admin-manual/maintenance/cli-tools/#generate-and-cache-xml-for-all-archival-descriptions Cache XML CLI task]
* [https://www.accesstomemory.org/docs/2.7/admin-manual/maintenance/cli-tools/#generate-a-finding-aid Generate a finding aid CLI task]

===Digital objects===

The 2.7 release includes a number of minor enhancements to the Digital object functionality in AtoM. The Digital object metadata area has been expanded to display separate details about the original and all derivatives, and the corresponding public visibility controls in the Visible Elements module have also been expanded to match. Administrators can now enable an option that will allow public users to include digital objects in their clipboard downloads. A new API endpoint has been added to allow authorized users to access the master digital object associated with a description. Additionally, thanks to a community pull request, subtitle and chapter tracks can now be uploaded alongside audio and video digital objects.

''General bug fixes and enhancements''

* #13497 - Video derivatives not generated when linking via URL

''Community pull requests from Matt Innes''

* #13459 - Reintroduce responsive audio/video
* #13471 - Clarify digital object derivative settings
* #13490 - Add support for subtitle and chapter tracks in video and audio digital objects

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/upload-digital-object/#add-subtitle-caption-and-or-chapter-files-to-audio-and-video Add subtitle, caption, or chapter tracks to video and audio uploads]

''Sponsored by an undisclosed institution''

* #13395 - Add option to include digital objects in clipboard exports

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/export-xml/#including-digital-objects-with-an-xml-clipboard-export Including digital objects with an XML clipboard export]
* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/csv-export/#including-digital-objects-in-a-clipboard-csv-export Including digital objects with a CSV clipboard export]
* [https://www.accesstomemory.org/docs/2.7/user-manual/administer/settings/#clipboard-do-export-setting Enable Clipboard digital object export functionality]

''Sponsored by Simon Fraser University Library''

* #13388 - Improve digital object metadata display
* #13417 - Digital object preservation copy displays UCT time stamps

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/upload-digital-object/#digital-object-metadata Digital object metadata]
* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/upload-digital-object/#digital-object-metadata-for-preservation-files Digital object metadata for preservation files]
* [https://www.accesstomemory.org/docs/2.7/user-manual/add-edit-content/rights/#configure-a-preservation-system-access-statement Configure a preservation system access statement]

''Sponsored by the Mills Archive''

* #13436 - Add API endpoint to download master digital object

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/dev-manual/api/download-do/ Download digital object API endpoint]

===Finding aids and reports===

We've addressed a few issues that prevented finding aids from generating when the Library of Congress EAD DTD was inaccessible by using a local DTD instead, and added a new administrative setting that can disable finding aid generation. When disabled, related finding view page links and advanced search filters will also be hidden in the user interface.

''General bug fixes and enhancements''

* #13247 - Finding aid generation sometimes fails reading DTD file
* #13590 - Finding aid generation fails due to a "403 Forbidden" error
* #13593 - Add the ability to turn off finding aid features in the AtoM UI

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/reports-printing/print-finding-aid/#finding-aid-settings Finding aid settings]

===Import and export===

The 2.7 release includes a new major module to support better CSV imports - the ability to validate a CSV prior to import, from the command-line or via the user interface. Additionally, an administrator can set validation to run automatically before any import if desired. We've also added a few command-line tasks to help verify imports or resolve issues - one task can audit a CSV against AtoM's database and report any rows that were not imported, and another task can delete descriptions created by a CSV import for cases where the import results were not as expected.

Other bug fixes in this release include the ability to export in CSV RAD note types for cast, credit, and signatures as well as the ability to export descriptions in CSV from the clipboard in RAD.

''General bug fixes and enhancements''

* #13287 - Repository CSV import fails when new terms added to Description Statuses in import file
* #13295 - Authority record CSV import fails when encountering new entity type (or variations in capitalization)
* #13457 - Create command line task to delete records created by a CSV import
* #13475 - Enhance AtoM's csv:check-import task to support pre-import validation
* #13481 - Some RAD notes fields don't appear in CSV exports
* #13483 - Description CSV exports from clipboard only exporting in ISAD
* #13561 - Add ability to use CSV check task on a directory full of CSV files
* #13567 - CSV authority record import requires identifier column be populated
* #13569 - Add CSV audit import task

''The development of this tool has been made possible by the Council of Nova Scotia Archives and the Library and Archives Canada's Documentary Heritage Communities Programs''

* #13508 - Integrate AtoM's CSV Validator into the Web UI

''Sponsored by UN Geneva Library''

* #13549 - Add slug column to CSV information object export

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/csv-validation/ CSV validation]
* [https://www.accesstomemory.org/docs/2.7/admin-manual/maintenance/cli-import-export/#delete-csv-io-import-cli Delete descriptions created by a CSV import from the command-line]
* [https://www.accesstomemory.org/docs/2.7/admin-manual/maintenance/cli-import-export/#audit-io-csv-import-cli Audit a CSV import]

===Rights===

It's now possible to enable the Copyright pop-up to apply to all digital objects in AtoM, without needing to individually apply Rights statements to each related record for the pop-up to trigger.

''Sponsored by the UN Archives Geneva''

* #13570 - Add ability to apply copyright pop-up globally without accompanying Rights statement

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/add-edit-content/rights/#copyright-pop-up Add a copyright statement]

===Scalability and performance===

''General bug fixes and enhancements''

* #13435 - Permission denied creating a new child description when Grant "create" on parent
* #13437 - Digital object authorization code is too complicated

''Sponsored by an undisclosed institution''

* #11556 - Make AtoM's clipboard work with the Varnish Cache web application accelerator
* #13389 - Support ability for reverse proxies like Varnish to cache content that's not in the default culture
* #13415 - An archival description with many descendants loads slowly when the DO carousel is enabled

===Settings===

''Sponsored by an undisclosed institution''

* #13411 - Add setting to enable or disable repository "upload limit" widget

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/administer/settings/#archival-institution-upload-limits Archival institution upload limits]

===Treeview===

''General bug fixes and enhancements''

* #13423 - Full-width treeview fails to load for descriptions with 900K+ children
* #13446 - Clicking on a description in the full-width treeview doesn't update the page URL
* #13491 - Terms treeview list tab's "Next" pager button does not work

===Other bug fixes and enhancements===

* #12628 - Drag and drop on full-width treeview makes it difficult for public users to scroll on mobile devices
* #13297 - Privacy policy static page cannot be deleted from the menus
* #13458 - PDF logo not included in PDF Finding Aids
* #13469 - Do not return 404 responses from search/autocomplete when there are no results
* #13506 - Copyright pop-up preview page no longer renders preview content
* #13586 - Certain special characters displays incorrectly in Web Page Title

''Community code contributions from Matt Innes''

* #10682 - Cannot create new authority record and add relationship at the same time
* #13218 - Error when adding function related to another
* #13499 - Various relation dialog fixes and improvements
* #13515 - Capitalize initial letter of languages in menu
* #13544 - Exclude narrower terms link and filter tag always link to description results

''Community code contribution from Jason Hildebrand and PeaceWorks Technology Solutions''

* #13441 - Improve Dockerfile layers caching

Releases/Release announcements/Release 2.7

2022-12-21T21:06:57Z

JennR:

{{#pagetitle:Release 2.7}}
[[Main Page]] > [[Releases]] > [[Releases/Release announcements]] > Release 2.7

'''Release date''': December 21, 2022

'''Download link''': [https://storage.accesstomemory.org/releases/atom-2.7.0.tar.gz atom-2.7.0.tar.gz]

'''Database schema version''': v192

'''Release 2.7''' is the first major AtoM release since July 2020, and includes new features, some dependency upgrades, accessibility improvements, as well as bug fixes. Some highlights include:

* An updated version of Bootstrap - both BS5 and BS2 are supported in 2.7
* The ability to use Central Authentication Service (CAS) for single sign on
* Enhanced Archivematica integration with the ability to download AIP and preservation files directly from AtoM
* Improved digital object metadata display area
* Introduction of a validation tool for CSV imports via the user interface
* New command line tasks to help verify imports and resolve issues

----
We’ve closed a number of issues as part of this release – you can view more details on each ticket in our issue tracker at the following links

* [https://projects.artefactual.com/versions/132 Release 2.7 Overview]
* [https://bit.ly/3Wxus5e 2.7 issues]

----

Visit the [https://www.accesstomemory.org/download/ Downloads] page to download the most recent release, and consult the 2.7 [https://www.accesstomemory.org/docs/2.7/admin-manual/installation/upgrading/ Upgrading] and [https://www.accesstomemory.org/docs/2.7/admin-manual/installation/linux/linux/ Installation] guides in our documentation for further information.

If you’re a brand new AtoM user, we suggest that you deploy a new install with BS5. If you are performing an upgrade and you have a custom theme we recommend you continue to use BS2 at this time.

An overview of some of the major changes in the 2.7 release is included below, followed by a list of links to relevant tickets, sponsors and contributors, and documentation for new features.

<admonition type="tip">
Issue numbers associated with new features and bug fixes listed below refer to the AtoM project issue tracker. Artefactual uses the issue tracker to track development tasks, feature requirements, quality assurance testing, and related development discussion. You can use the numbers to search for the related issue ticket in our Issue tracker - often the tickets will include more information on how the feature was implemented.

For more information, see: [[Resources/Issue_tracker|Issue tracker]]
</admonition>

__TOC__

-----

===Accessibility===

Community contributor [https://github.com/mInnes-archives Matt Innes] has contributed a number of minor accessibility enhancements to the latest AtoM release, addressing elements such as adding missing aria labels or instructions, better tab navigation flow and general page structure improvements, removal of redundant elements affecting accessibility, etc. These changes do not affect the look or feel of AtoM, but should provide some quality of life improvements for users with assistive technologies such as screen readers.

''Community contributions from Matt Innes''

* #13535 - Enhance accessibility support of various AtoM template elements

====Bootstrap 5====

AtoM will be integrating Bootstrap 5 into AtoM. Bootstrap is a framework for developing websites and is used in AtoM to provide theme templates to administrators
This updated version of Bootstrap provides a number of improvements such as better security, responsiveness and accessibility.

The new version of Bootstrap enables significant accessibility and responsiveness improvements over previous AtoM versions and it has better responsiveness for public users accommodating portable devices with varying screen sizes making the websites more easily accessible independent of device.

The new version of Bootstrap will be available in future releases of AtoM and more information will be provided in future forum announcements.

'''Related documentation'''
* [https://accesstomemory.org/docs/2.7/user-manual/administer/themes/#themes Themes]

===Accessions===

This release sees some additional incremental support for elements of the Canadian Archival Accession Information Standard ([http://archivescanada.ca/CWG_AccessionStandard CAAIS]). In this release, we have added a basic module for managing events in conformance with CAAIS Element [http://archivescanada.ca/CWG_AccessionStandard#5.1_e 5.1], which are "the actions taken by repository staff throughout the accession process." The 5.1.1 Event Type field is linked to a new Accession Events taxonomy that can be customized by an administrator as needed.

''General bug fixes and enhancements''

* #13466 - Accession donors are not indexed properly

''Sponsored by the Government of the Northwest Territories''

* #13315 - Add ability to associate events with accession records

'''Related documentation''':

* [https://www.accesstomemory.org/docs/2.7/user-manual/add-edit-content/accessions/#add-accession-events Add events to an accession record]

===Authentication===

AtoM now supports use of the Central Authentication Service ([https://apereo.github.io/cas/4.2.x/protocol/CAS-Protocol-Specification.html CAS]) protocol for single sign-on and authentication management. Additionally, the previously undocumented support for LDAP now has configuration instructions in the Administrator's manual (on the same page as the CAS documentation linked below).

''Sponsored by Simon Fraser University Archives''

* #13383 - Support CAS single sign-on

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/admin-manual/customization/authentication/#cas-enabling Enable CAS authentication]

===Archivematica integration===

For users who are using AtoM with [https://www.archivematica.org Archivematica], administrators who have Archivematica access can now download AIP and preservation files directly from AtoM. This coincides with the digital object metadata improvements described in the [[Releases/Roadmap#Digital_objects|Digital objects]] section below.

''Sponsored by Simon Fraser University Archives''

* #13351 - Support AIP download from AtoM UI for authorized users

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/upload-digital-object/#digital-object-metadata-for-preservation-files Digital object metadata for preservation files]

===Authority records===

This release adds a minor enhancement that will provide a warning notification to authenticated users when a duplicate authority record identifier is entered. This warning is never shown to public users, similar to existing warnings in the standards-based templates.

''Sponsored by an undisclosed institution''

* #13373 - Display warning for duplicate authority record identifiers

===Command-line tasks===

In addition to the CLI enhancements described in the Import/Export section below, this release also includes a new task to help system administrators remove temporary files, such as old saved clipboards and downloads found in the jobs subdirectory. When troubleshooting upgrade issues related to the database schema version, users an also use a new option on the <code>tools:upgrade</code> task to run individual schema migrations, in case one is missed during an upgrade process.

Another feature that has been added as part of this release is replacing the AtoM web installer with a command line driver installation. This feature addresses the installation timeout via the web browser by moving the AtoM installation steps. It should simplify the installation process overall, better support automated deployments, and resolve the timeout issues resulting from the web installer's current use.

''General bug fixes and enhancements''

* #13368 - Add CLI option to migration task to run individual migrations
* #13440 - Add ability for tools:expire-data to delete temp files
* #13452 - Replace AtoM's web installer with a command-line driven installation process
* #13500 - Add CLI task to generate finding aids

''Sponsored by Mills Archive''

* #13361 - Add option to cache XML task to generate only EAD or DC XML

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/admin-manual/maintenance/cli-tools/#delete-temporary-data-saved-clipboards-and-downloads Expire data CLI task]
* [https://www.accesstomemory.org/docs/2.7/admin-manual/maintenance/cli-tools/#generate-and-cache-xml-for-all-archival-descriptions Cache XML CLI task]
* [https://www.accesstomemory.org/docs/2.7/admin-manual/maintenance/cli-tools/#generate-a-finding-aid Generate a finding aid CLI task]

===Digital objects===

The 2.7 release includes a number of minor enhancements to the Digital object functionality in AtoM. The Digital object metadata area has been expanded to display separate details about the original and all derivatives, and the corresponding public visibility controls in the Visible Elements module have also been expanded to match. Administrators can now enable an option that will allow public users to include digital objects in their clipboard downloads. A new API endpoint has been added to allow authorized users to access the master digital object associated with a description. Additionally, thanks to a community pull request, subtitle and chapter tracks can now be uploaded alongside audio and video digital objects.

''General bug fixes and enhancements''

* #13497 - Video derivatives not generated when linking via URL

''Community pull requests from Matt Innes''

* #13459 - Reintroduce responsive audio/video
* #13471 - Clarify digital object derivative settings
* #13490 - Add support for subtitle and chapter tracks in video and audio digital objects

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/upload-digital-object/#add-subtitle-caption-and-or-chapter-files-to-audio-and-video Add subtitle, caption, or chapter tracks to video and audio uploads]

''Sponsored by an undisclosed institution''

* #13395 - Add option to include digital objects in clipboard exports

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/export-xml/#including-digital-objects-with-an-xml-clipboard-export Including digital objects with an XML clipboard export]
* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/csv-export/#including-digital-objects-in-a-clipboard-csv-export Including digital objects with a CSV clipboard export]
* [https://www.accesstomemory.org/docs/2.7/user-manual/administer/settings/#clipboard-do-export-setting Enable Clipboard digital object export functionality]

''Sponsored by Simon Fraser University Library''

* #13388 - Improve digital object metadata display
* #13417 - Digital object preservation copy displays UCT time stamps

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/upload-digital-object/#digital-object-metadata Digital object metadata]
* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/upload-digital-object/#digital-object-metadata-for-preservation-files Digital object metadata for preservation files]
* [https://www.accesstomemory.org/docs/2.7/user-manual/add-edit-content/rights/#configure-a-preservation-system-access-statement Configure a preservation system access statement]

''Sponsored by the Mills Archive''

* #13436 - Add API endpoint to download master digital object

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/dev-manual/api/download-do/ Download digital object API endpoint]

===Finding aids and reports===

We've addressed a few issues that prevented finding aids from generating when the Library of Congress EAD DTD was inaccessible by using a local DTD instead, and added a new administrative setting that can disable finding aid generation. When disabled, related finding view page links and advanced search filters will also be hidden in the user interface.

''General bug fixes and enhancements''

* #13247 - Finding aid generation sometimes fails reading DTD file
* #13590 - Finding aid generation fails due to a "403 Forbidden" error
* #13593 - Add the ability to turn off finding aid features in the AtoM UI

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/reports-printing/print-finding-aid/#finding-aid-settings Finding aid settings]

===Import and export===

The 2.7 release includes a new major module to support better CSV imports - the ability to validate a CSV prior to import, from the command-line or via the user interface. Additionally, an administrator can set validation to run automatically before any import if desired. We've also added a few command-line tasks to help verify imports or resolve issues - one task can audit a CSV against AtoM's database and report any rows that were not imported, and another task can delete descriptions created by a CSV import for cases where the import results were not as expected.

Other bug fixes in this release include the ability to export in CSV RAD note types for cast, credit, and signatures as well as the ability to export descriptions in CSV from the clipboard in RAD.

''General bug fixes and enhancements''

* #13287 - Repository CSV import fails when new terms added to Description Statuses in import file
* #13295 - Authority record CSV import fails when encountering new entity type (or variations in capitalization)
* #13457 - Create command line task to delete records created by a CSV import
* #13475 - Enhance AtoM's csv:check-import task to support pre-import validation
* #13481 - Some RAD notes fields don't appear in CSV exports
* #13483 - Description CSV exports from clipboard only exporting in ISAD
* #13561 - Add ability to use CSV check task on a directory full of CSV files
* #13567 - CSV authority record import requires identifier column be populated
* #13569 - Add CSV audit import task

''The development of this tool has been made possible by the Council of Nova Scotia Archives and the Library and Archives Canada's Documentary Heritage Communities Programs''

* #13508 - Integrate AtoM's CSV Validator into the Web UI

''Sponsored by UN Geneva Library''

* #13549 - Add slug column to CSV information object export

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/csv-validation/ CSV validation]
* [https://www.accesstomemory.org/docs/2.7/admin-manual/maintenance/cli-import-export/#delete-csv-io-import-cli Delete descriptions created by a CSV import from the command-line]
* [https://www.accesstomemory.org/docs/2.7/admin-manual/maintenance/cli-import-export/#audit-io-csv-import-cli Audit a CSV import]

===Rights===

It's now possible to enable the Copyright pop-up to apply to all digital objects in AtoM, without needing to individually apply Rights statements to each related record for the pop-up to trigger.

''Sponsored by the UN Archives Geneva''

* #13570 - Add ability to apply copyright pop-up globally without accompanying Rights statement

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/add-edit-content/rights/#copyright-pop-up Add a copyright statement]

===Scalability and performance===

''General bug fixes and enhancements''

* #13435 - Permission denied creating a new child description when Grant "create" on parent
* #13437 - Digital object authorization code is too complicated

''Sponsored by an undisclosed institution''

* #11556 - Make AtoM's clipboard work with the Varnish Cache web application accelerator
* #13389 - Support ability for reverse proxies like Varnish to cache content that's not in the default culture
* #13415 - An archival description with many descendants loads slowly when the DO carousel is enabled

===Settings===

''Sponsored by an undisclosed institution''

* #13411 - Add setting to enable or disable repository "upload limit" widget

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/administer/settings/#archival-institution-upload-limits Archival institution upload limits]

===Treeview===

''General bug fixes and enhancements''

* #13423 - Full-width treeview fails to load for descriptions with 900K+ children
* #13446 - Clicking on a description in the full-width treeview doesn't update the page URL
* #13491 - Terms treeview list tab's "Next" pager button does not work

===Other bug fixes and enhancements===

* #12628 - Drag and drop on full-width treeview makes it difficult for public users to scroll on mobile devices
* #13297 - Privacy policy static page cannot be deleted from the menus
* #13458 - PDF logo not included in PDF Finding Aids
* #13469 - Do not return 404 responses from search/autocomplete when there are no results
* #13506 - Copyright pop-up preview page no longer renders preview content
* #13586 - Certain special characters displays incorrectly in Web Page Title

''Community code contributions from Matt Innes''

* #10682 - Cannot create new authority record and add relationship at the same time
* #13218 - Error when adding function related to another
* #13499 - Various relation dialog fixes and improvements
* #13515 - Capitalize initial letter of languages in menu
* #13544 - Exclude narrower terms link and filter tag always link to description results

''Community code contribution from Jason Hildebrand and PeaceWorks Technology Solutions''

* #13441 - Improve Dockerfile layers caching

Releases/Release announcements/Release 2.7

2022-12-21T20:51:30Z

JennR:

{{#pagetitle:Release 2.7}}
[[Main Page]] > [[Releases]] > [[Releases/Release announcements]] > Release 2.7

'''Release date''': December 21, 2022

'''Download link''': [https://storage.accesstomemory.org/releases/atom-2.7.0.tar.gz atom-2.7.0.tar.gz]

'''Database schema version''': v192

'''Release 2.7''' is the first major AtoM release since July 2020, and includes new features, some dependency upgrades, accessibility improvements, as well as bug fixes. Some highlights include:

* An updated version of Bootstrap - both BS5 and BS2 are supported in 2.7
* The ability to use Central Authentication Service (CAS) for single sign on
* Enhanced Archivematica integration with the ability to download AIP and preservation files directly from AtoM
* Improved digital object metadata display area
* Introduction of a validation tool for CSV imports via the user interface
* New command line tasks to help verify imports and resolve issues

----
We’ve closed a number of issues as part of this release – you can view more details on each ticket in our issue tracker at the following links

* [https://projects.artefactual.com/versions/132 Release 2.7 Roadmap / Overview]
* [https://bit.ly/3Wxus5e 2.7 issues]

----

Visit the [https://www.accesstomemory.org/download/ Downloads] page to download the most recent release, and consult the 2.7 [https://www.accesstomemory.org/docs/2.7/admin-manual/installation/upgrading/ Upgrading] and [https://www.accesstomemory.org/docs/2.7/admin-manual/installation/linux/linux/ Installation] guides in our documentation for further information.

If you’re a brand new AtoM user, we suggest that you deploy a new install with BS5. If you are performing an upgrade and you have a custom theme we recommend you continue to use BS2 at this time.

An overview of some of the major changes in the 2.7 release is included below, followed by a list of links to relevant tickets, sponsors and contributors, and documentation for new features.

<admonition type="tip">
Issue numbers associated with new features and bug fixes listed below refer to the AtoM project issue tracker. Artefactual uses the issue tracker to track development tasks, feature requirements, quality assurance testing, and related development discussion. You can use the numbers to search for the related issue ticket in our Issue tracker - often the tickets will include more information on how the feature was implemented.

For more information, see: [[Resources/Issue_tracker|Issue tracker]]
</admonition>

__TOC__

-----

===Accessibility===

Community contributor [https://github.com/mInnes-archives Matt Innes] has contributed a number of minor accessibility enhancements to the latest AtoM release, addressing elements such as adding missing aria labels or instructions, better tab navigation flow and general page structure improvements, removal of redundant elements affecting accessibility, etc. These changes do not affect the look or feel of AtoM, but should provide some quality of life improvements for users with assistive technologies such as screen readers.

''Community contributions from Matt Innes''

* #13535 - Enhance accessibility support of various AtoM template elements

====Bootstrap 5====

AtoM will be integrating Bootstrap 5 into AtoM. Bootstrap is a framework for developing websites and is used in AtoM to provide theme templates to administrators
This updated version of Bootstrap provides a number of improvements such as better security, responsiveness and accessibility.

The new version of Bootstrap enables significant accessibility and responsiveness improvements over previous AtoM versions and it has better responsiveness for public users accommodating portable devices with varying screen sizes making the websites more easily accessible independent of device.

The new version of Bootstrap will be available in future releases of AtoM and more information will be provided in future forum announcements.

'''Related documentation'''
* [https://accesstomemory.org/docs/2.7/user-manual/administer/themes/#themes Themes]

===Accessions===

This release sees some additional incremental support for elements of the Canadian Archival Accession Information Standard ([http://archivescanada.ca/CWG_AccessionStandard CAAIS]). In this release, we have added a basic module for managing events in conformance with CAAIS Element [http://archivescanada.ca/CWG_AccessionStandard#5.1_e 5.1], which are "the actions taken by repository staff throughout the accession process." The 5.1.1 Event Type field is linked to a new Accession Events taxonomy that can be customized by an administrator as needed.

''General bug fixes and enhancements''

* #13466 - Accession donors are not indexed properly

''Sponsored by the Government of the Northwest Territories''

* #13315 - Add ability to associate events with accession records

'''Related documentation''':

* [https://www.accesstomemory.org/docs/2.7/user-manual/add-edit-content/accessions/#add-accession-events Add events to an accession record]

===Authentication===

AtoM now supports use of the Central Authentication Service ([https://apereo.github.io/cas/4.2.x/protocol/CAS-Protocol-Specification.html CAS]) protocol for single sign-on and authentication management. Additionally, the previously undocumented support for LDAP now has configuration instructions in the Administrator's manual (on the same page as the CAS documentation linked below).

''Sponsored by Simon Fraser University Archives''

* #13383 - Support CAS single sign-on

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/admin-manual/customization/authentication/#cas-enabling Enable CAS authentication]

===Archivematica integration===

For users who are using AtoM with [https://www.archivematica.org Archivematica], administrators who have Archivematica access can now download AIP and preservation files directly from AtoM. This coincides with the digital object metadata improvements described in the [[Releases/Roadmap#Digital_objects|Digital objects]] section below.

''Sponsored by Simon Fraser University Archives''

* #13351 - Support AIP download from AtoM UI for authorized users

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/upload-digital-object/#digital-object-metadata-for-preservation-files Digital object metadata for preservation files]

===Authority records===

This release adds a minor enhancement that will provide a warning notification to authenticated users when a duplicate authority record identifier is entered. This warning is never shown to public users, similar to existing warnings in the standards-based templates.

''Sponsored by an undisclosed institution''

* #13373 - Display warning for duplicate authority record identifiers

===Command-line tasks===

In addition to the CLI enhancements described in the Import/Export section below, this release also includes a new task to help system administrators remove temporary files, such as old saved clipboards and downloads found in the jobs subdirectory. When troubleshooting upgrade issues related to the database schema version, users an also use a new option on the <code>tools:upgrade</code> task to run individual schema migrations, in case one is missed during an upgrade process.

Another feature that has been added as part of this release is replacing the AtoM web installer with a command line driver installation. This feature addresses the installation timeout via the web browser by moving the AtoM installation steps. It should simplify the installation process overall, better support automated deployments, and resolve the timeout issues resulting from the web installer's current use.

''General bug fixes and enhancements''

* #13368 - Add CLI option to migration task to run individual migrations
* #13440 - Add ability for tools:expire-data to delete temp files
* #13452 - Replace AtoM's web installer with a command-line driven installation process
* #13500 - Add CLI task to generate finding aids

''Sponsored by Mills Archive''

* #13361 - Add option to cache XML task to generate only EAD or DC XML

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/admin-manual/maintenance/cli-tools/#delete-temporary-data-saved-clipboards-and-downloads Expire data CLI task]
* [https://www.accesstomemory.org/docs/2.7/admin-manual/maintenance/cli-tools/#generate-and-cache-xml-for-all-archival-descriptions Cache XML CLI task]
* [https://www.accesstomemory.org/docs/2.7/admin-manual/maintenance/cli-tools/#generate-a-finding-aid Generate a finding aid CLI task]

===Digital objects===

The 2.7 release includes a number of minor enhancements to the Digital object functionality in AtoM. The Digital object metadata area has been expanded to display separate details about the original and all derivatives, and the corresponding public visibility controls in the Visible Elements module have also been expanded to match. Administrators can now enable an option that will allow public users to include digital objects in their clipboard downloads. A new API endpoint has been added to allow authorized users to access the master digital object associated with a description. Additionally, thanks to a community pull request, subtitle and chapter tracks can now be uploaded alongside audio and video digital objects.

''General bug fixes and enhancements''

* #13497 - Video derivatives not generated when linking via URL

''Community pull requests from Matt Innes''

* #13459 - Reintroduce responsive audio/video
* #13471 - Clarify digital object derivative settings
* #13490 - Add support for subtitle and chapter tracks in video and audio digital objects

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/upload-digital-object/#add-subtitle-caption-and-or-chapter-files-to-audio-and-video Add subtitle, caption, or chapter tracks to video and audio uploads]

''Sponsored by an undisclosed institution''

* #13395 - Add option to include digital objects in clipboard exports

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/export-xml/#including-digital-objects-with-an-xml-clipboard-export Including digital objects with an XML clipboard export]
* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/csv-export/#including-digital-objects-in-a-clipboard-csv-export Including digital objects with a CSV clipboard export]
* [https://www.accesstomemory.org/docs/2.7/user-manual/administer/settings/#clipboard-do-export-setting Enable Clipboard digital object export functionality]

''Sponsored by Simon Fraser University Library''

* #13388 - Improve digital object metadata display
* #13417 - Digital object preservation copy displays UCT time stamps

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/upload-digital-object/#digital-object-metadata Digital object metadata]
* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/upload-digital-object/#digital-object-metadata-for-preservation-files Digital object metadata for preservation files]
* [https://www.accesstomemory.org/docs/2.7/user-manual/add-edit-content/rights/#configure-a-preservation-system-access-statement Configure a preservation system access statement]

''Sponsored by the Mills Archive''

* #13436 - Add API endpoint to download master digital object

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/dev-manual/api/download-do/ Download digital object API endpoint]

===Finding aids and reports===

We've addressed a few issues that prevented finding aids from generating when the Library of Congress EAD DTD was inaccessible by using a local DTD instead, and added a new administrative setting that can disable finding aid generation. When disabled, related finding view page links and advanced search filters will also be hidden in the user interface.

''General bug fixes and enhancements''

* #13247 - Finding aid generation sometimes fails reading DTD file
* #13590 - Finding aid generation fails due to a "403 Forbidden" error
* #13593 - Add the ability to turn off finding aid features in the AtoM UI

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/reports-printing/print-finding-aid/#finding-aid-settings Finding aid settings]

===Import and export===

The 2.7 release includes a new major module to support better CSV imports - the ability to validate a CSV prior to import, from the command-line or via the user interface. Additionally, an administrator can set validation to run automatically before any import if desired. We've also added a few command-line tasks to help verify imports or resolve issues - one task can audit a CSV against AtoM's database and report any rows that were not imported, and another task can delete descriptions created by a CSV import for cases where the import results were not as expected.

Other bug fixes in this release include the ability to export in CSV RAD note types for cast, credit, and signatures as well as the ability to export descriptions in CSV from the clipboard in RAD.

''General bug fixes and enhancements''

* #13287 - Repository CSV import fails when new terms added to Description Statuses in import file
* #13295 - Authority record CSV import fails when encountering new entity type (or variations in capitalization)
* #13457 - Create command line task to delete records created by a CSV import
* #13475 - Enhance AtoM's csv:check-import task to support pre-import validation
* #13481 - Some RAD notes fields don't appear in CSV exports
* #13483 - Description CSV exports from clipboard only exporting in ISAD
* #13561 - Add ability to use CSV check task on a directory full of CSV files
* #13567 - CSV authority record import requires identifier column be populated
* #13569 - Add CSV audit import task

''The development of this tool has been made possible by the Council of Nova Scotia Archives and the Library and Archives Canada's Documentary Heritage Communities Programs''

* #13508 - Integrate AtoM's CSV Validator into the Web UI

''Sponsored by UN Geneva Library''

* #13549 - Add slug column to CSV information object export

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/csv-validation/ CSV validation]
* [https://www.accesstomemory.org/docs/2.7/admin-manual/maintenance/cli-import-export/#delete-csv-io-import-cli Delete descriptions created by a CSV import from the command-line]
* [https://www.accesstomemory.org/docs/2.7/admin-manual/maintenance/cli-import-export/#audit-io-csv-import-cli Audit a CSV import]

===Rights===

It's now possible to enable the Copyright pop-up to apply to all digital objects in AtoM, without needing to individually apply Rights statements to each related record for the pop-up to trigger.

''Sponsored by the UN Archives Geneva''

* #13570 - Add ability to apply copyright pop-up globally without accompanying Rights statement

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/add-edit-content/rights/#copyright-pop-up Add a copyright statement]

===Scalability and performance===

''General bug fixes and enhancements''

* #13435 - Permission denied creating a new child description when Grant "create" on parent
* #13437 - Digital object authorization code is too complicated

''Sponsored by an undisclosed institution''

* #11556 - Make AtoM's clipboard work with the Varnish Cache web application accelerator
* #13389 - Support ability for reverse proxies like Varnish to cache content that's not in the default culture
* #13415 - An archival description with many descendants loads slowly when the DO carousel is enabled

===Settings===

''Sponsored by an undisclosed institution''

* #13411 - Add setting to enable or disable repository "upload limit" widget

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/administer/settings/#archival-institution-upload-limits Archival institution upload limits]

===Treeview===

''General bug fixes and enhancements''

* #13423 - Full-width treeview fails to load for descriptions with 900K+ children
* #13446 - Clicking on a description in the full-width treeview doesn't update the page URL
* #13491 - Terms treeview list tab's "Next" pager button does not work

===Other bug fixes and enhancements===

* #12628 - Drag and drop on full-width treeview makes it difficult for public users to scroll on mobile devices
* #13297 - Privacy policy static page cannot be deleted from the menus
* #13458 - PDF logo not included in PDF Finding Aids
* #13469 - Do not return 404 responses from search/autocomplete when there are no results
* #13506 - Copyright pop-up preview page no longer renders preview content
* #13586 - Certain special characters displays incorrectly in Web Page Title

''Community code contributions from Matt Innes''

* #10682 - Cannot create new authority record and add relationship at the same time
* #13218 - Error when adding function related to another
* #13499 - Various relation dialog fixes and improvements
* #13515 - Capitalize initial letter of languages in menu
* #13544 - Exclude narrower terms link and filter tag always link to description results

''Community code contribution from Jason Hildebrand and PeaceWorks Technology Solutions''

* #13441 - Improve Dockerfile layers caching

Releases/Release announcements/Release 2.7

2022-12-21T20:46:04Z

JennR: Created page with "{{#pagetitle:Release 2.7}} Main Page > Releases > Releases/Release announcements > Release 2.7 '''Release date''': December 21, 2022 '''Download link''': [https:..."

{{#pagetitle:Release 2.7}}
[[Main Page]] > [[Releases]] > [[Releases/Release announcements]] > Release 2.7

'''Release date''': December 21, 2022

'''Download link''': [https://storage.accesstomemory.org/releases/atom-2.7.0.tar.gz atom-2.7.0.tar.gz]

'''Database schema version''': v192

'''Release 2.7''' is the first major AtoM release since July 2020, and includes new features, some dependency upgrades, accessibility improvements, as well as bug fixes. Some highlights include:

* An updated version of Bootstrap - both BS5 and BS2 are supported in 2.7
* The ability to use Central Authentication Service (CAS) for single sign on
* Enhanced Archivematica integration with the ability to download AIP and preservation files directly from AtoM
* Improved digital object metadata display area
* Introduction of a validation tool for CSV imports via the user interface
* New command line tasks to help verify imports and resolve issues

----
We’ve closed a number of issues as part of this release – you can view more details on each ticket in our issue tracker at the following links

* [https://projects.artefactual.com/versions/132 Release 2.7 Roadmap / Overview]
* [https://bit.ly/3Wxus5e issues]

----

Visit the [https://www.accesstomemory.org/download/ Downloads] page to download the most recent release, and consult the 2.7 [https://www.accesstomemory.org/docs/2.7/admin-manual/installation/upgrading/ Upgrading] and [https://www.accesstomemory.org/docs/2.7/admin-manual/installation/linux/linux/ Installation] guides in our documentation for further information.

If you’re a brand new AtoM user, we suggest that you deploy a new install with BS5. If you are performing an upgrade and you have a custom theme we recommend you continue to use BS2 at this time.

An overview of some of the major changes in the 2.7 release is included below, followed by a list of links to relevant tickets, sponsors and contributors, and documentation for new features.

<admonition type="tip">
Issue numbers associated with new features and bug fixes listed below refer to the AtoM project issue tracker. Artefactual uses the issue tracker to track development tasks, feature requirements, quality assurance testing, and related development discussion. You can use the numbers to search for the related issue ticket in our Issue tracker - often the tickets will include more information on how the feature was implemented.

For more information, see: [[Resources/Issue_tracker|Issue tracker]]
</admonition>

__TOC__

-----

===Accessibility===

Community contributor [https://github.com/mInnes-archives Matt Innes] has contributed a number of minor accessibility enhancements to the latest AtoM release, addressing elements such as adding missing aria labels or instructions, better tab navigation flow and general page structure improvements, removal of redundant elements affecting accessibility, etc. These changes do not affect the look or feel of AtoM, but should provide some quality of life improvements for users with assistive technologies such as screen readers.

''Community contributions from Matt Innes''

* #13535 - Enhance accessibility support of various AtoM template elements

====Bootstrap 5====

AtoM will be integrating Bootstrap 5 into AtoM. Bootstrap is a framework for developing websites and is used in AtoM to provide theme templates to administrators
This updated version of Bootstrap provides a number of improvements such as better security, responsiveness and accessibility.

The new version of Bootstrap enables significant accessibility and responsiveness improvements over previous AtoM versions and it has better responsiveness for public users accommodating portable devices with varying screen sizes making the websites more easily accessible independent of device.

The new version of Bootstrap will be available in future releases of AtoM and more information will be provided in future forum announcements.

'''Related documentation'''
* [https://accesstomemory.org/docs/2.7/user-manual/administer/themes/#themes Themes]

===Accessions===

This release sees some additional incremental support for elements of the Canadian Archival Accession Information Standard ([http://archivescanada.ca/CWG_AccessionStandard CAAIS]). In this release, we have added a basic module for managing events in conformance with CAAIS Element [http://archivescanada.ca/CWG_AccessionStandard#5.1_e 5.1], which are "the actions taken by repository staff throughout the accession process." The 5.1.1 Event Type field is linked to a new Accession Events taxonomy that can be customized by an administrator as needed.

''General bug fixes and enhancements''

* #13466 - Accession donors are not indexed properly

''Sponsored by the Government of the Northwest Territories''

* #13315 - Add ability to associate events with accession records

'''Related documentation''':

* [https://www.accesstomemory.org/docs/2.7/user-manual/add-edit-content/accessions/#add-accession-events Add events to an accession record]

===Authentication===

AtoM now supports use of the Central Authentication Service ([https://apereo.github.io/cas/4.2.x/protocol/CAS-Protocol-Specification.html CAS]) protocol for single sign-on and authentication management. Additionally, the previously undocumented support for LDAP now has configuration instructions in the Administrator's manual (on the same page as the CAS documentation linked below).

''Sponsored by Simon Fraser University Archives''

* #13383 - Support CAS single sign-on

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/admin-manual/customization/authentication/#cas-enabling Enable CAS authentication]

===Archivematica integration===

For users who are using AtoM with [https://www.archivematica.org Archivematica], administrators who have Archivematica access can now download AIP and preservation files directly from AtoM. This coincides with the digital object metadata improvements described in the [[Releases/Roadmap#Digital_objects|Digital objects]] section below.

''Sponsored by Simon Fraser University Archives''

* #13351 - Support AIP download from AtoM UI for authorized users

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/upload-digital-object/#digital-object-metadata-for-preservation-files Digital object metadata for preservation files]

===Authority records===

This release adds a minor enhancement that will provide a warning notification to authenticated users when a duplicate authority record identifier is entered. This warning is never shown to public users, similar to existing warnings in the standards-based templates.

''Sponsored by an undisclosed institution''

* #13373 - Display warning for duplicate authority record identifiers

===Command-line tasks===

In addition to the CLI enhancements described in the Import/Export section below, this release also includes a new task to help system administrators remove temporary files, such as old saved clipboards and downloads found in the jobs subdirectory. When troubleshooting upgrade issues related to the database schema version, users an also use a new option on the <code>tools:upgrade</code> task to run individual schema migrations, in case one is missed during an upgrade process.

Another feature that has been added as part of this release is replacing the AtoM web installer with a command line driver installation. This feature addresses the installation timeout via the web browser by moving the AtoM installation steps. It should simplify the installation process overall, better support automated deployments, and resolve the timeout issues resulting from the web installer's current use.

''General bug fixes and enhancements''

* #13368 - Add CLI option to migration task to run individual migrations
* #13440 - Add ability for tools:expire-data to delete temp files
* #13452 - Replace AtoM's web installer with a command-line driven installation process
* #13500 - Add CLI task to generate finding aids

''Sponsored by Mills Archive''

* #13361 - Add option to cache XML task to generate only EAD or DC XML

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/admin-manual/maintenance/cli-tools/#delete-temporary-data-saved-clipboards-and-downloads Expire data CLI task]
* [https://www.accesstomemory.org/docs/2.7/admin-manual/maintenance/cli-tools/#generate-and-cache-xml-for-all-archival-descriptions Cache XML CLI task]
* [https://www.accesstomemory.org/docs/2.7/admin-manual/maintenance/cli-tools/#generate-a-finding-aid Generate a finding aid CLI task]

===Digital objects===

The 2.7 release includes a number of minor enhancements to the Digital object functionality in AtoM. The Digital object metadata area has been expanded to display separate details about the original and all derivatives, and the corresponding public visibility controls in the Visible Elements module have also been expanded to match. Administrators can now enable an option that will allow public users to include digital objects in their clipboard downloads. A new API endpoint has been added to allow authorized users to access the master digital object associated with a description. Additionally, thanks to a community pull request, subtitle and chapter tracks can now be uploaded alongside audio and video digital objects.

''General bug fixes and enhancements''

* #13497 - Video derivatives not generated when linking via URL

''Community pull requests from Matt Innes''

* #13459 - Reintroduce responsive audio/video
* #13471 - Clarify digital object derivative settings
* #13490 - Add support for subtitle and chapter tracks in video and audio digital objects

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/upload-digital-object/#add-subtitle-caption-and-or-chapter-files-to-audio-and-video Add subtitle, caption, or chapter tracks to video and audio uploads]

''Sponsored by an undisclosed institution''

* #13395 - Add option to include digital objects in clipboard exports

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/export-xml/#including-digital-objects-with-an-xml-clipboard-export Including digital objects with an XML clipboard export]
* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/csv-export/#including-digital-objects-in-a-clipboard-csv-export Including digital objects with a CSV clipboard export]
* [https://www.accesstomemory.org/docs/2.7/user-manual/administer/settings/#clipboard-do-export-setting Enable Clipboard digital object export functionality]

''Sponsored by Simon Fraser University Library''

* #13388 - Improve digital object metadata display
* #13417 - Digital object preservation copy displays UCT time stamps

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/upload-digital-object/#digital-object-metadata Digital object metadata]
* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/upload-digital-object/#digital-object-metadata-for-preservation-files Digital object metadata for preservation files]
* [https://www.accesstomemory.org/docs/2.7/user-manual/add-edit-content/rights/#configure-a-preservation-system-access-statement Configure a preservation system access statement]

''Sponsored by the Mills Archive''

* #13436 - Add API endpoint to download master digital object

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/dev-manual/api/download-do/ Download digital object API endpoint]

===Finding aids and reports===

We've addressed a few issues that prevented finding aids from generating when the Library of Congress EAD DTD was inaccessible by using a local DTD instead, and added a new administrative setting that can disable finding aid generation. When disabled, related finding view page links and advanced search filters will also be hidden in the user interface.

''General bug fixes and enhancements''

* #13247 - Finding aid generation sometimes fails reading DTD file
* #13590 - Finding aid generation fails due to a "403 Forbidden" error
* #13593 - Add the ability to turn off finding aid features in the AtoM UI

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/reports-printing/print-finding-aid/#finding-aid-settings Finding aid settings]

===Import and export===

The 2.7 release includes a new major module to support better CSV imports - the ability to validate a CSV prior to import, from the command-line or via the user interface. Additionally, an administrator can set validation to run automatically before any import if desired. We've also added a few command-line tasks to help verify imports or resolve issues - one task can audit a CSV against AtoM's database and report any rows that were not imported, and another task can delete descriptions created by a CSV import for cases where the import results were not as expected.

Other bug fixes in this release include the ability to export in CSV RAD note types for cast, credit, and signatures as well as the ability to export descriptions in CSV from the clipboard in RAD.

''General bug fixes and enhancements''

* #13287 - Repository CSV import fails when new terms added to Description Statuses in import file
* #13295 - Authority record CSV import fails when encountering new entity type (or variations in capitalization)
* #13457 - Create command line task to delete records created by a CSV import
* #13475 - Enhance AtoM's csv:check-import task to support pre-import validation
* #13481 - Some RAD notes fields don't appear in CSV exports
* #13483 - Description CSV exports from clipboard only exporting in ISAD
* #13561 - Add ability to use CSV check task on a directory full of CSV files
* #13567 - CSV authority record import requires identifier column be populated
* #13569 - Add CSV audit import task

''The development of this tool has been made possible by the Council of Nova Scotia Archives and the Library and Archives Canada's Documentary Heritage Communities Programs''

* #13508 - Integrate AtoM's CSV Validator into the Web UI

''Sponsored by UN Geneva Library''

* #13549 - Add slug column to CSV information object export

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/import-export/csv-validation/ CSV validation]
* [https://www.accesstomemory.org/docs/2.7/admin-manual/maintenance/cli-import-export/#delete-csv-io-import-cli Delete descriptions created by a CSV import from the command-line]
* [https://www.accesstomemory.org/docs/2.7/admin-manual/maintenance/cli-import-export/#audit-io-csv-import-cli Audit a CSV import]

===Rights===

It's now possible to enable the Copyright pop-up to apply to all digital objects in AtoM, without needing to individually apply Rights statements to each related record for the pop-up to trigger.

''Sponsored by the UN Archives Geneva''

* #13570 - Add ability to apply copyright pop-up globally without accompanying Rights statement

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/add-edit-content/rights/#copyright-pop-up Add a copyright statement]

===Scalability and performance===

''General bug fixes and enhancements''

* #13435 - Permission denied creating a new child description when Grant "create" on parent
* #13437 - Digital object authorization code is too complicated

''Sponsored by an undisclosed institution''

* #11556 - Make AtoM's clipboard work with the Varnish Cache web application accelerator
* #13389 - Support ability for reverse proxies like Varnish to cache content that's not in the default culture
* #13415 - An archival description with many descendants loads slowly when the DO carousel is enabled

===Settings===

''Sponsored by an undisclosed institution''

* #13411 - Add setting to enable or disable repository "upload limit" widget

'''Related documentation'''

* [https://www.accesstomemory.org/docs/2.7/user-manual/administer/settings/#archival-institution-upload-limits Archival institution upload limits]

===Treeview===

''General bug fixes and enhancements''

* #13423 - Full-width treeview fails to load for descriptions with 900K+ children
* #13446 - Clicking on a description in the full-width treeview doesn't update the page URL
* #13491 - Terms treeview list tab's "Next" pager button does not work

===Other bug fixes and enhancements===

* #12628 - Drag and drop on full-width treeview makes it difficult for public users to scroll on mobile devices
* #13297 - Privacy policy static page cannot be deleted from the menus
* #13458 - PDF logo not included in PDF Finding Aids
* #13469 - Do not return 404 responses from search/autocomplete when there are no results
* #13506 - Copyright pop-up preview page no longer renders preview content
* #13586 - Certain special characters displays incorrectly in Web Page Title

''Community code contributions from Matt Innes''

* #10682 - Cannot create new authority record and add relationship at the same time
* #13218 - Error when adding function related to another
* #13499 - Various relation dialog fixes and improvements
* #13515 - Capitalize initial letter of languages in menu
* #13544 - Exclude narrower terms link and filter tag always link to description results

''Community code contribution from Jason Hildebrand and PeaceWorks Technology Solutions''

* #13441 - Improve Dockerfile layers caching

Releases/Release announcements

2022-12-21T18:37:01Z

JennR: /* AtoM (2.x) releases */

{{#pagetitle: Release announcements }}

[[Main Page]] > [[Releases]] > Releases/Release announcements

Here are detailed lists of the new features, enhancements, and bug fixes in each ICA-AtoM and AtoM release.

<admonition type="tip">
Looking for information on upcoming releases? Check the [[Releases/Roadmap|Roadmap]] page!
</admonition>

== AtoM (2.x) releases ==

AtoM 2 releases are available on the AtoM website, at: https://www.accesstomemory.org/download/

* [[Releases/Release announcements/Release 2.7|Release 2.7]] (December 21, 2022)
* [[Releases/Release announcements/Release 2.6.4|Release 2.6.4]] (April 15, 2021)
* [[Releases/Release announcements/Release 2.6.3|Release 2.6.3]] (March 31, 2021)
* [[Releases/Release announcements/Release 2.6.2|Release 2.6.2]] (February 4, 2021)
* [[Releases/Release announcements/Release 2.6.1|Release 2.6.1]] (October 21, 2020)
* [[Releases/Release announcements/Release 2.6|Release 2.6]] (July 14, 2020)
* [[Releases/Release announcements/Release 2.5.4|Release 2.5.4]] (May 5, 2020)
* [[Releases/Release announcements/Release 2.5.3|Release 2.5.3]] (October 30, 2019)
* [[Releases/Release announcements/Release 2.5.2|Release 2.5.2]] (August 29, 2019)
* [[Releases/Release announcements/Release 2.5.1|Release 2.5.1]] (July 3, 2019)
* [[Releases/Release announcements/Release 2.5|Release 2.5]] (May 9, 2019)
* [[Releases/Release announcements/Release 2.4.1|Release 2.4.1]] (November 2, 2018)
* [[Releases/Release announcements/Release 2.4|Release 2.4]] (September 5, 2017)
* [[Releases/Release announcements/Release 2.3.1|Release 2.3.1]] (February 14th, 2017)
* [[Releases/Release announcements/Release 2.3|Release 2.3]] (July 19, 2016)
* [[Releases/Release announcements/Release 2.2.1|Release 2.2.1]] (February 10, 2016)
* [[Releases/Release announcements/Release 2.2|Release 2.2]] (July 10, 2015)
* [[Releases/Release announcements/Release 2.1.2|Release 2.1.2 translation pack]] (February 10, 2015 )
* [[Releases/Release announcements/Release 2.1.1|Release 2.1.1 security upgrade]] (January 28, 2015)
* [[Releases/Release announcements/Release 2.1|Release 2.1.0]] (September 22, 2014)
* [[Releases/Release announcements/Release 2.1.1|Release 2.0.2 security upgrade]] (January 28, 2015)
* [[Releases/Release announcements/Release 2.0.1|Release 2.0.1]] (December 16, 2013)
* [[Releases/Release announcements/Release 2.0.0|Release 2.0.0]] (October 7, 2013)

== ICA-AtoM (1.x) releases ==

For more information about ICA-AtoM, our earlier version of the AtoM software, please visit the ICA-AtoM wiki: https://www.ica-atom.org/doc/Main_Page

* [[Releases/Release announcements/Release 1.4|Release 1.4]] (unscheduled)
* [[Releases/Release announcements/Release 2.1.1|Release 1.3.2 security upgrade]] (January 28, 2015)
* [[Releases/Release announcements/Release 1.3.1|Release 1.3.1]] (May 7, 2013)
* [[Releases/Release announcements/Release 1.3|Release 1.3]] (August 27, 2012)
* [[Releases/Release announcements/Release 1.2.1|Release 1.2.1]] (June 28, 2012)
* [[Releases/Release announcements/Release 1.2|Release 1.2]] (November 29, 2011)
* [[Releases/Release announcements/Release 1.1|Release 1.1]] (November 22, 2010)
* [[Releases/Release announcements/Release 1.0.9-beta|Release 1.0.9-beta]] (May 17, 2010)
* [[Releases/Release announcements/Release 1.0.8-beta|Release 1.0.8-beta]] (November 2, 2009)
* [[Releases/Release announcements/Release 1.0.7-beta|Release 1.0.7-beta]] (June 1, 2009)
* [[Releases/Release announcements/Release 1.0.6-beta|Release 1.0.6-beta]] (April 27, 2009)
* [[Releases/Release announcements/Release 1.0.5-beta|Release 1.0.5-beta]] (March 11, 2009)
* [[Releases/Release announcements/Release 1.0.4-beta|Release 1.0.4-beta]] (November 17, 2008)
* [[Releases/Release announcements/Release 1.0.3-beta|Release 1.0.3-beta]] (October 9, 2008)
* [[Releases/Release announcements/Release 1.0.2-beta|Release 1.0.2-beta]] (August 8, 2008)
* [[Releases/Release announcements/Release 1.0.1-beta|Release 1.0.1-beta]] (July 22, 2008)
* [[Releases/Release announcements/Release 1.0-beta|Release 1.0-beta]] (July 1, 2008)

-----

* [[Releases|Back to Releases]]
* [[Main Page|AtoM wiki home]]

[[Category:Releases]]

Community/Success stories

2020-10-21T16:17:10Z

JennR: /* Success stories */

{{#pagetitle: Success stories }}
[[Main Page]] > [[Community]] > Success stories

On this page is a list of community success stories relating to both [https://www.accesstomemory.org/ AtoM] and [https://www.ica-atom.org/ ICA-AtoM]. We know there are a lot more success stories out there, so please help us populate this page. Feel free to [[Special:UserLogin|add your own]] success story here!

<admonition type="seealso">
* [[Community/Users|List of AtoM users]]
*[[Community/Community resources|Community resources]]
</admonition>

__TOC__

==Success stories==

'''October 21, 2020''' - The Saskatchewan Council for Archives and Archivists and the University of Saskatchewan have re-launched the new [https://memorysask.ca/ Memory Sask-SAIN] AtoM database.

SCAA’s website announced the launch on October 1, providing this summary:

''It may look similar, but now searches of the full shared content of SCAA member institutions can be made in one place, including the ability to search within different photographs collections making MemorySask – SAIN a powerful tool for research.

''In late 2019, U of S, with funding and staff support from SCAA, contracted Artefactual Systems to merge the two SAIN databases. This was a major undertaking involving both custom programming and manual review of descriptions. The work on the SAIN merger project was completed in March. Since then, several contributing institutions have been adding and updating entries through a temporary hosting arrangement. This arrangement was facilitated by U of S, which hosts the public database, to minimize further downtime as their IT staff were focused on support required due to the pandemic.''

''Now with the U of S able to take-on the hosting duties from Artefactual the public launch is on the horizon.''

Congratulations on a successful re-launch of your database – especially during a pandemic and challenging work times. Well done, all!

-----

'''February 19, 2020''' - The Association for Manitoba Archives ([http://mbarchives.ca/ AMA]) announces the successful conclusion of a massive, multi-year project to update the provincial portal's ([https://main.lib.umanitoba.ca/ MAIN], which runs AtoM) subject headings " to be more inclusive and respectful of Manitoba’s Indigenous people." From the details added to MAIN about the project:

''Over a period of six years, the MAIN-LCSH Working Group of the AMA, along with the technical support of Artefactual Systems and the financial support of the AMA, worked diligently to realize this goal. By undertaking a consultation process with Indigenous communities in Manitoba, as well as with librarians and archivists around the world, the subject terminology now employed in MAIN is not only more appropriate for describing archival records by or about Manitoba’s Indigenous people, but the descriptions remain highly discoverable and consistent with metadata standards and best practices.''

''As this work was influenced by others working in this realm, we too encourage reuse of our work in other libraries and archives. The list of terms that were added, changed, or deleted is available here'': https://doi.org/10.5203/ss_ama.main_bon.chr.2015.1.

''It is our hope that other institutions will be able to build on what we have done and implement culturally appropriate Indigenous subject headings in catalogues and repositories around the world.''

''The AMA is committed to ensuring that this resource continues to adapt to cultural and societal shifts that necessitate changes in subject headings.''

Congratulations on the successful implementation of an important project!

* Visit the [https://main.lib.umanitoba.ca/ Manitoba Archival Information Network] (MAIN), provincial archival portal for the AMA
* Read more about the [https://main.lib.umanitoba.ca/indigenous-subject-headings Indigenous Subject Headings] on MAIN
* Browse all [https://main.lib.umanitoba.ca/subjects Subject headings in MAIN]
* View the list of modified and deleted Library of Congress Subject Heading (LCSH) terms from the project: https://doi.org/10.5203/ss_ama.main_bon.chr.2015.1
* Read a paper written about the project by Christine Bone and Brett Lougheed: http://winnspace.uwinnipeg.ca/handle/10680/1321

-----

'''February 7, 2020''' - The [http://www.saskarchives.com/ Provincial Archives of Saskatchewan] announce the launch of their new AtoM catalog. This comes after a long migration, development, and theming contract with Artefactual Systems. Some excerpts from the public announcement found on the News and events page of the PAS website:

''“This online catalogue puts the rich history of our province directly at the fingertips of our citizens,” said Minister Responsible for the Provincial Archives of Saskatchewan Ken Cheveldayoff. “This will enable a broader audience to access historical documents anytime, anywhere whether their research be personal or academic.”''

''Researchers can search over 900,000 descriptions of records from the Permanent Collection of the Provincial Archives. The catalogue also provides online access to more than 300,000 digitized original archival records, primarily photographs and textual records. New content is added as records are processed and digital projects are completed.''

''“Our new catalogue provides a fresh, streamlined approach to accessing our holdings,” Provincial Archivist, Linda McIntyre said. “It enables us to make content available online quickly and easily, for research use across the province and around the world.”''

Congratulations on the successful launch!

* See the new PAS catalogue here: https://search.saskarchives.com/
* View the [https://www.saskarchives.com/news-and-events News and events section] of the PAS website

Note: The News and Events section of the PAS website does not maintain historical news posts or provide individual links per announcement. A screenshot of the AtoM launch announcement on February 7th, 2020 is included below.

[[File:pas-atom-launch-2020-02-07.png|center|500px|thumb| PAS AtoM launch announcement, February 7, 2020]]

-----

'''October 25, 2018''' - Mount Royal University's [https://library.mtroyal.ca/searchandfind/ourcollections/archivesandspecialcollections Archives and Special Collections] has now publicly launched its new AtoM-based descriptive database, called [https://archives.mtroyal.ca/ Archives Search]. In a [https://blogs.mtroyal.ca/library/2018/10/25/new-online-access-to-rare-archival-collections/ blog post] announcing the launch, MRU notes:

''The Archives and Special Collections now offers an online database that allows Library users to access rare primary sources from the classroom or even from the comfort of their own homes. Archives Search, launched on October 25, contains descriptions of over 2,600 historical records held by the Archives and Special Collections. It also contains over 1,400 digitized photographs and documents, allowing far greater access to these sources while also helping to preserve fragile originals.''

''"Archives contain the unique unpublished primary sources that history is written from," explains Archivist and Special Collections Librarian Peter Houston. The launch of this new online resource is a big step towards his goal of connecting as many students and faculty as possible to the Archives’ valuable collections so that they can be used for teaching and research.''

Congratulations on the launch!

* [https://blogs.mtroyal.ca/library/2018/10/25/new-online-access-to-rare-archival-collections/ See the launch announcement blog post]
* [https://archives.mtroyal.ca/ Visit MRU's Archives Search site]

-----

'''October 15, 2018''' - The [https://vancouver.ca/your-government/city-of-vancouver-archives.aspx City of Vancouver Archives] (CVA) has launched its first release of Vancouver Organizing Committee for the 2010 Olympic and Paralympic Winter Games (VANOC) born-digital material. Over 12,000 digital photographs from the 2010 Olympic Torch Relay (OTR) are [https://searcharchives.vancouver.ca/otr-torchbearer-photos now available] to the public. This represents a significant milestone in the CVA's digital preservation program, and a successful test of Archivematica's ability to ingest large numbers of files and automatically upload access copies and descriptive metadata to CVA's [https://searcharchives.vancouver.ca/ online database].

As part of the Host City Agreement for the 2010 Winter Olympic Games, the CVA was designated the repository for VANOC's records of archival value and at the end of the Games, VANOC transferred 70 metres of analogue records and 25 TB of born-digital material. The City invested in CVA's digital preservation capacity with funding from the Olympic Legacy Fund, and CVA became one of the first institutions to allocate resources to the development of Archivematica.

Digital Archivist Glenn Dingwall has been working with the VANOC records, time permitting, since 2012, and writes about the Olympic Torch Relay photographs on the CVA blog, [https://www.vancouverarchives.ca/2018/10/11/2010-olympic-torch-relay-photographs-now-available/#more-7217 AuthentiCity].

[[File:OTRroute.png|center|500px|thumb| Olympic Torch Relay Route]]

-----

'''October 4, 2018''' The [https://www.edmonton.ca/city_government/edmonton_archives/city-of-edmonton-archives.aspx City of Edmonton Archives] officially launches its new [https://cityarchives.edmonton.ca/ AtoM catalogue!] The Edmonton team held a public launch celebration at Edmonton City Hall to help kick-off the relaunch and celebrate [http://archivesalberta.org/programs-and-services/archives-week/ Alberta Archives Week 2018].

[[File:edmonton-AtoM-launch-2018.jpg|center|500px|thumb| The City of Edmonton Archives launch event announcement]]

City Archivist Kathryn Ivany spoke to the Star Edmonton following the launch:

''The three-year project to overhaul the site culminated at the end of July, she said, when the new site hit the web. Since the refresh, she estimates the online catalogue holds about 50-per-cent more digital records, but it won’t end there.''

''"We’re still adding to the website, even now." Ivany said. "Archives always have lots of material that’s not available yet because we keep getting bus loads of material coming in. People will always find something new on the website."'' Congratulations to everyone on a successful launch!

* [https://cityarchives.edmonton.ca/ Explore the new City of Edmonton Archives catalogue]
* [http://transformingedmonton.ca/city-archives-launches-new-website/ Read about the launch on the City's ''Transforming Edmonton'' blog]
* [https://www.thestar.com/edmonton/2018/10/04/website-upgrades-give-edmontons-city-archives-a-digital-dusting.html Read the coverage in the Star Edmononton]

-----

'''April 10, 2018''' - The National Library of Sweden ([https://www.kb.se/ Kungliga Biblioteket]) launches its new AtoM catalogue! Launched under the name "Arken," the new archival directory includes two of KB's personal archives that have been recently been nominated for inclusion in the UNESCO [https://en.unesco.org/programme/mow/register Memory of the World Register]: the [https://arken.kb.se/SE-S-HS-L179 Dag Hammarskjöld Collection] and [https://arken.kb.se/SE-S-HS-L230 Astrid Lindgren's archives]. The award is given to archives, museums or documents that are considered to be of value to all humankind. A Swedish press release accompanying the launch noted that Arken "''replaces the older directory service Ediffah, which KB previously used to list their personal archives and manuscripts. The new service is based on Open Source software Access to Memory (AtoM), which is easier to use, develop and manage in the long term. The choice of AtoM also depends on the ability to display digitized material from the collections and to manage links to authority data from, for example, Libris.''" Congratulations to everyone at NLS for a successful launch!

* [https://www.kb.se/om-oss/nyheter/nyhetsarkiv/2018-04-10-kulturgiganter-far-nytt-hem-i-kbs-katalogtjanst-arken.html See the press release] (Swedish)
* [https://arken.kb.se/ Explore Arken] (Swedish)
* [https://www.kb.se/hitta-och-bestall/om-samlingar-och-material/personarkiv.html Read more about what you'll find in Arken] (Swedish)

-----

'''February 8, 2018''' - The City of Victoria Archives launches their new [https://archives.victoria.ca/ online catalogue], powered by Access to Memory. Multiple local newspaper articles about the new catalogue note that at launch time, the site already contains "more than 10,000 digitized archival photos and records." A local City of Victoria Council member called the launch "a massive step forward." The articles go on to list some of the exciting content that can be found in the catalogue, including:

* ''A collection of photos from H.U. Knight including candid photos of Emily Carr in her studio in 1934.''
* ''A large collection from photographer W.E. John, known for his quirky and candid shots of people living their lives throughout the city, particularly in the 1960s. The collection includes photographs from a “love-in” held in Beacon Hill Park in 1967.''
* ''Photos chronicling evocative moments in the city’s history, including soldiers marching off to war, haying on Dallas Road, wooden paving blocks being pulled up on Yates Street in 1947 and soldiers digging trenches in Beacon Hill Park as part of a training exercise prior to deployment in the First World War.''

Congratulations to the City of Victoria Archives on a successful launch!

* Explore the [https://archives.victoria.ca/ City of Victoria Archives' Online Search]
* Read about the launch in the [http://www.timescolonist.com/news/local/peek-into-victoria-s-history-gets-easier-with-searchable-online-archive-1.23169319 Times Colonist]
* Read about the launch on [http://victoriabuzz.com/2018/02/city-victoria-archives-introduces-new-online-search/ Victoria Buzz]

-----

'''January 25, 2018''' - The University of Toronto launches ''Discover Archives'', a shared portal for exploring archival holdings at the University of Toronto and its federated colleges. At launch time, the site contained over 57,000 descriptions from 11 participating institutions, including:

* OISE Library Special Collections
* Thomas Fisher Rare Book Library
* Trinity College Archives
* University of St. Michael's College Archives
* University of St. Michael's College, John M. Kelly Library, Special Collections
* University of Toronto Archives and Records Management Services
* University of Toronto Media Commons (Media Archive)
* University of Toronto Music Library
* University of Toronto Scarborough Library, Archives & Special Collections
* Victoria University Archives
* Victoria University Library - Special Collections

[[File:discover-archives-launch.jpg|center|700px|thumb| The Discover Archives launch announcement poster]]

In the [https://groups.google.com/d/msg/ica-atom-users/AjGqPIMYEvk/D_LukFalBgAJ announcement] made in the AtoM user forum, Kelli Babcock (Digital Initiatives Librarian, UofT Libraries) adds the following on behalf of the Discover Archives Steering Committee:

''I also wanted to note here that the AtoM Users community and fantastic work and documentation from Artefactual Systems have been invaluable while developing Discover Archives - thank you all. We hope to contribute more of our knowledge to the AtoM community as we grow and maintain Discover Archives.''

Congratulations to everyone at UofT and the Discover Archives Steering Committee for a successful launch!

* [https://discoverarchives.library.utoronto.ca Explore the University of Toronto's Discover Archives Portal]
* See the announcement in the [https://groups.google.com/d/msg/ica-atom-users/AjGqPIMYEvk/D_LukFalBgAJ AtoM User Forum]

-----

'''January 17, 2018''' - The Fashion Institute of Technology Library’s [http://www.fitnyc.edu/library/sparc/index.php Special Collections and College Archives (SPARC)] is excited to formally announce [https://atom-sparc.fitnyc.edu/ SPARC Connect], our online discovery platform using Access to Memory (AtoM) that allows users to search across our collections.

SPARC Connect supports the discovery and use of the rare and unique materials held in the collection. Collection level descriptions and downloadable finding aids of SPARC’s holdings have always been available through FIT Library’s catalogue, [http://fit.sunyconnect.suny.edu:4690/F Stylecat]. The beauty of SPARC Connect is having finding aids available to be searched in their entirety, at the series, folder, and item level. Users are able to see search results across collections and narrow down using faceted fields such as subject, name, or collection.

Under the leadership of Karen Trivette SPARC has worked to provide the greatest possible access to our collections. SPARC started using AtoM in 2014. Since that time SPARC has undergone a $4 million renovation and moved twice.

In an effort to make as many of our 385+ collections available through SPARC Connect, new finding aids are added weekly. Highlights include:
*[https://atom-sparc.fitnyc.edu/lucile-ltd-records-1910-1925-1 Lucile, Ltd. Records, 1910-1925]
*[https://atom-sparc.fitnyc.edu/international-costume-carte-de-visite-photographs International costume carte-de-visite photographs, 1860-1880]
*[https://atom-sparc.fitnyc.edu/hattie-carnegie-sketches-1940-5 Hattie Carnegie sketches, 1940-1955]
*[https://atom-sparc.fitnyc.edu/eric-de-juan-sketch-collection-1927-1990 Eric de Juan sketch collection, 1927-1989]
*[https://atom-sparc.fitnyc.edu/museum-at-fit-records-1948-2015 Museum at FIT records, 1948-2015]
*[https://atom-sparc.fitnyc.edu/eleanor-lambert-collection-1943-2003 Eleanor Lambert collection, 1943-2003]

-----

'''July 26, 2017''' - Dalhousie Univerity Libraries announces major additions to their AtoM catalogue. The following is copied from an announcement sent out on the SAA's Archives & Archivists (A&A) List, posted by Creighton Barrett, the Digital Archivist at the Dalhousie University Archives:

''The Dalhousie Libraries is very pleased to announce the publication of new finding aids and digital content in its Archives Catalogue and Online Collections:'' http://findingaids.library.dal.ca/

''With this update, the University Archives reaches two milestones: the catalogue now has more than 250,000 archival descriptions and more than 10,000 digital objects. Highlights include:''
* ''More than 2,400 digitized photographs in the Dalhousie University Photograph Collection:'' http://findingaids.library.dal.ca/dalhousie-university-photograph-collection/digitalobject/browse
* ''Digitized issues of "The Dalhousian" a student newspaper published in 1914 as part of a campaign for a new student building:'' http://findingaids.library.dal.ca/the-dalhousian
* ''Digitized issues of "Dal News," a newspaper published by Dalhousie University:'' http://findingaids.library.dal.ca/dalhousie-news-2/digitalobject/browse
* ''Digitized issues of "University News," the predecessor to "Dal News":'' http://findingaids.library.dal.ca/university-news-1976/digitalobject/browse
* ''More than 900 digitized slides and photographs of Arctic communities in the early 1960s from the Barbara Hinds fonds:'' http://findingaids.library.dal.ca/barbara-hinds-fonds/digitalobject/browse ''(this project was funded by Nova Scotia's Provincial Archival Development Program)''

''We have been actively digitizing material in anticipation of Dalhousie's 200th anniversary to be celebrated in 2018, and will continue to add digital content in the coming months. Visit the Dal 200 website for more information about bicentennial celebrations:'' https://dal200.ca/

''Our catalogue was launched in January 2015 and is proudly powered by the open source Access to Memory (AtoM) software. Visit the Archives’ website for more information about our collections and services:'' https://dal.ca/archives

Congratulations Dalhousie University!

-----

'''June 01, 2017''' - The Oregon Historical Society ([http://ohs.org/ OHS]) launches their new public catalogue using AtoM - the [https://digitalcollections.ohs.org/ Oregon Historical Society Digital Collections]. Local newspaper the Beaverton Valley Times ran an article on the site's launch, which included the following:

''This new website allows online public access to a rich variety of materials from the OHS Research Library, including items from the manuscript, photograph, film and oral history collections. Behind the scenes, these files are safeguarded using a series of digital preservation workflows, systems and storage processes called the OHS Digital Vault.''

''"We're proud to announce the availability of this platform, which we view as a cornerstone of our organizational mission to make Oregon's history open and accessible to all," said OHS digital archivist Mathieu Deschaine. "We look forward to continued additions that will illustrate the breadth and diversity of our holdings and encourage their use for teaching, learning and research."''

Congratulations, OHS!

* Explore the [https://digitalcollections.ohs.org/ OHS Digital Collections]
* Read the article in the [http://pamplinmedia.com/bvt/17-features/361411-240797-oregon-historical-society-launches-online-archives Beaverton Valley Times]

-----

'''May 25, 2017''' - The City of Winnipeg Archives formally announces the launch of its upgraded catalog, Winnipeg in Focus, using AtoM. The City of Winnipeg began the process of migrating to a new archival management system in 2015 - the last stages of the migration were completed by Artefactual Systems, along with custom theming of the new site. In an announcement made on the Canadian archival mailing list, ARCAN-L, Sarah Ramsden, Archivist at the City of Winnipeg, said the following:

''Winnipeg in Focus has been expanded from a database of historical photographs to the premier search tool for the City's archival collection. The application now contains archival records (reports, letters, and a growing number of photographs) that can be searched and accessed online. It also includes new information about records that support discovery and use of the City's rich archival collection.''

''The new and improved application...''

* ''Is a database for archival descriptions and records in electronic form.''
* ''Includes all of the historical photographs from the previous application and additional content.''
* ''Has improved in the areas of look, design, and functionality as a result of moving to the web-based application Access to Memory (AtoM).''
* ''Will expand gradually as staff members add content over time.''

Congratulations to the City of Winnipeg, and welcome to the AtoM community!

* Explore the new site: [http://winnipeginfocus.winnipeg.ca/ Winnipeg in Focus]
* See the 2015 Addendum report submitted to City Council approving the project [http://clkapps.winnipeg.ca/DMIS/ViewDoc.asp?DocId=14611&SectionId=408946&InitUrl=/DMIS/Documents/fi/2015/a14611 here]

-----

'''May 17, 2017''' - The Saskatchewan Archival Information Network ([http://scaa.sk.ca/sain-database/ SAIN]), two portal sites maintained by the Saskatchewan Council for Archives & Archivists ([http://www.scaa.sk.ca/home/ SCAA]), is relaunched using AtoM 2. SAIN was one of ICA-AtoM's earliest adopters, but held on to the 1.x version while completing local customizations that allow for better institutional scoping when searching and browsing in a multi-repository instance. Now contributed back to the public project, the "Institutional scoping" feature was mostly developed in-house at the University of Saskatchewan Library, and then completed by Artefactual with funding from the U of S and the Saskatchewan Council for Archives and Archivists. The SAIN sites also include a custom theme - of this Tim Hutchinson, Head of the University of Saskatchewan's Archives & Special Collections, writes:

''"This was created by one of our developers within days of returning from AtoM Camp SFU, building on the default Dominion theme. Beyond integrating design elements of the new SCAA website, the responsiveness has been improved a bit compared to the default theme - mainly achieved, as I understand, by moving the browse and search elements out of the block with icons for language, bookmark etc. We also contributed a fix to a bug that was preventing the facets from displaying via mobile."''

Congratulations to the SCAA on a successful relaunch!

* Explore the [http://sain.scaa.sk.ca/collections/ SAIN Collections Database]
* Explore the [http://sain.scaa.sk.ca/items/ SAIN Photographs Database]
* Read an announcement about the launch in the [https://groups.google.com/d/msg/ica-atom-users/HXAAz57ljAs/yNtr7QlvAwAJ AtoM User Forum]

-----

'''May 11, 2017''' - Our second AtoM Camp, and our first in the United Kingdom, is complete! ''AtoM Camp Cambridge'' was hosted by St. John's College at the University of Cambridge, in Cambridge, UK from Tuesday, May 9th to Thursday, May 11th, 2017. The camp featured 3 days of sessions geared to users of all levels delivered by Community Counselors Jenny Mitcham of the [https://borthcat.york.ac.uk/ Borthwick Institute for Archives] at the University of York, and Pete Vox of [http://imagiz.com/ IMAGIZ].

* See the AtoM Camp Cambridge wiki page: [[Community/Camps/SJC2017|AtoM Camp Cambridge 2017]]
* Read a blog post about the Camp from Community Counselor Jenny Mitcham of the [https://borthcat.york.ac.uk/ Borthwick Institute for Archives] at the University of York: [http://digital-archiving.blogspot.com/2017/05/atom-camp-take-aways.html AtoM Camp take aways]

-----

'''March 22, 2017''' - Artefactual completes its first ever AtoM Camp! ''AtoM Camp SFU'' was hosted by the Simon Fraser University Archives, in Vancouver, British Columbia from Monday, March 20 to Wednesday, March 22, 2017. The camp featured 3 days of sessions geared to users of all levels delivered by Community Counselor Tim Hutchinson, Head of the University of Saskatchewan's Archives & Special Collections, as well as Artefactual staff.

* See the AtoM Camp SFU wiki page: [[Community/Camps/SFU2017|AtoM Camp SFU 2017]]
* Read a blog post about the Camp from a participant, Emily Lonie of the City of Coquitlam Archives: [http://www.thingsimfondsof.com/atom-camp/ "So this one time, at AtoM Camp..."]

-----

'''April 7, 2016''' - After years of planning, the [https://www.york.ac.uk/borthwick/ Borthwick Institute for Archives] at the [http://www.york.ac.uk/ University of York] launches their new catalogue - using AtoM! Jenny Mitcham writes on her blog, "[http://digital-archiving.blogspot.ca/2016/04/our-atom-catalogue-is-now-live.html Digital Archiving at the University of York]," that:

''My main aim in getting involved in this project was to create a stable base to build a digital archive on.''

''If you build a digital archive on wobbly foundations there is a strong chance that it will fall over.''

''Much safer to build it on top of a system established as the single point of truth for all accessions information your organisation holds. A system which will become the means by which you disseminate information about your digital holdings (alongside the physical ones) and enable users to access copies of born digital and digitised material.''

''Finally we have such a solution in place!''

We're proud to see AtoM chosen to be part of the Borthwick Institute's stable base.

* [http://digital-archiving.blogspot.ca/2016/04/our-atom-catalogue-is-now-live.html Read the full blog post here]
* [https://borthcat.york.ac.uk/ Explore the Borthwick Institute for Archives catalogue]

-----

'''March 18, 2016''' - [https://twitter.com/Jenny_Mitcham Jenny Mitcham] from the Borthwick Institute for Archives at the University of York has recently written an excellent, thorough, and balanced piece on implementing AtoM. Titled [http://digital-archiving.blogspot.ca/2016/03/a-is-for-atom.html 'A' is for AtoM], the blog post list an A-Z set of thoughts, considerations, challenges, and useful tips her team encountered when setting up AtoM as the system of record for the University's archival holdings. Some excerpts we were thrilled about:

''F is for Friendly Advice''

''Though there is much detail in the AtoM documentation, anyone starting to use a new system such as AtoM will inevitably get to the point where they need to speak to someone, or see another implementation. The AtoM mailing list and the staff at Artefactual Systems are friendly and helpful and it is easy to get quick answers to specific questions. ...''

''J is for Just Start!''

''...Reading the documentation is essential but testing and experimenting with AtoM are really the best ways of working it out. Only by importing different datasets into AtoM or by creating new ones direct into the web form did we really understand how it worked and how this impacted on our own internal workflows. Learn by doing!''

''K is for Kittens (because they are never really free)''

''...On top of this, there will undoubtedly be things that you want AtoM to do that it doesn't yet do. If you are implementing AtoM, have a budget for funding further developments. Sponsored developments will then benefit the wider AtoM community and together we can make AtoM better and better. Quite early on in our AtoM implementation project we funded a small piece of work to include covering dates within the accessions module of AtoM as we felt that this was important information to record during the accessioning process and we did not want to lose this data from our existing accessions records when we imported them into the system. Of course we are hoping this feature will also be valuable for other AtoM users. There will undoubtedly be other feature developments we will sponsor in the future.''

And this honest but optimistic nugget:

''N is for Not Perfect''

''AtoM (like all complex systems) has its limitations. It ticks many boxes for us but it does not tick them all. There are several areas where we think it could improve and we have been discussing these with the user community and developers and hope to influence its roadmap. As with all open source solutions, rather than complaining about what it doesn't do well, the user community should be working together to solve problems and support improvements. AtoM is not perfect but we are confident that it is moving in the right direction and getting better all the time.''

We fully agree! Thanks so much for sharing such a thorough and interesting story about your experiences with AtoM, Jen!

* [http://digital-archiving.blogspot.ca/2016/03/a-is-for-atom.html Read the full blog post here]
-----

'''March 16, 2016''' - The British Columbia Institute of Technology Archives [http://www.bcit.ca/archives/ BCIT Archives] launches a new AtoM instance to allow public users to search their archival holdings. In a related [http://commons.bcit.ca/library/2016/03/16/bcit-archives-new-search/ blog post], the BCIT Archives notes the following about choosing AtoM:

''The BCIT Archives chose the open source software AtoM for several reasons:''

* ''AtoM was developed under the guidance of the International Council on Archives using international archival standards.''
* ''Starting from archival standards ensured that the end result would be a software that was able to reflect the complex nature of archival records.''
* ''It has an active community of users worldwide.''
* ''This active open source community means that updates are frequent and user-driven.''
* ''And finally, the lead developers on AtoM, Artefactual Systems, are our neighbours, based in New Westminster.''

Congratulations on a successful launch!

* [http://atom.bcit.ca/ Explore the BCIT Archives & Special Collections online AtoM catalogue]
* [http://commons.bcit.ca/library/2016/03/16/bcit-archives-new-search/ Read the launch announcement blog post]

-----

'''September 3, 2015''' - The Jewish Museum & Archives of BC formally launches a brand new [http://jewishmuseum.ca/ website], which includes an AtoM instance for all archival holdings. A formal press release, posted in the British Columbia archival mailing list ([http://aabc.ca/resources/electronic-mailing-list/ Archives-BC], included the following:

''Implementing the archives database system, Access to Memory (AtoM), the new jewishmuseum.ca grants researchers unprecedented access to thousands of documents, photos, audio and video documenting the 150 year history of Jews in BC.''

''"For the first time in the history of the JMABC, we have the capability of providing online access to the treasures in the archives, while at the same time adhering to important archival standards,” notes archivist Jennifer Yuhasz. “We are excited to join the vast community of professional archives already using AtoM, including UNESCO, World Bank Group Archives, and most of the provincial, municipal and university archives and libraries across BC."''

In addition to contributions from several donors and grant programs, the Jewish Museum & Archives of BC managed this impressive launch in part via a successful [https://www.indiegogo.com/projects/bringing-bc-s-jewish-history-to-everyone#/story crowdfunding campaign] to raise funds for the new website and data migration to AtoM, to which over 100 participants managed to exceed the target goal of $18,000.

An [http://jewishmuseum.ca/searching-the-new-archives-catalogue/ earlier post] on the new website's blog also helped familiarize users with the new AtoM-based catalogue. Congratulations to everyone involved in this successful migration and launch!

* [http://jewishmuseum.ca/ See the new JMABC website]
* [http://archives.jewishmuseum.ca/ Explore the JMABC AtoM catalogue]
* [http://jewishmuseum.ca/searching-the-new-archives-catalogue/ See the blog post]
* [https://www.indiegogo.com/projects/bringing-bc-s-jewish-history-to-everyone#/story Check out the crowdfunding campaign story]

-----

'''August 18, 2015''' - The State Records Office of Western Australia launches its new AtoM site, after a multi-year testing, migration, and development project. The accompanying announcement, titled "One Giant Step for SRO," says of AtoM: "''The need for a fast, modern archive management system and responsive public access catalogue led us to the search which identified AtoM, an open source software system, as the most likely candidate. All the systems we looked at required some modification to enable us to meet Australian descriptive standards, as well as international standards, but AtoM seemed to us to be the most flexible, and it had the blessing of the International Council of Archives.''" SRO Western Australia worked with [http://www.gaiaresources.com.au/ Gaia Resources] for their AtoM development needs, and over the course of the project, Gaia Resources developers contributed several bug fixes and minor features to the public AtoM releases as well. According to an announcement post in the AtoM User Forum, the State Records Office has migrated "''804,024 items; 4,843 series; 1,919 organisations; 67 images (and growing).''" Congratulations to everyone involved!

* [http://www.sro.wa.gov.au/blogs/one-giant-step-sro Read the catalogue launch announcement]
* [http://www.sro.wa.gov.au/blogs/aeon-atom See all blog posts related to the AtoM migration project - "From AEON to AtoM"]
* [https://archive.sro.wa.gov.au/ Explore the new AtoM site of the State Records Office of Western Australia]
* [https://groups.google.com/d/msg/ica-atom-users/Q5wcSfv2fKw/c7zz_rBlCQAJ See the announcement in the User Forum]
* [http://www.gaiaresources.com.au/archives-online/ See a related Sept 10 2015 post about the work on Gaia Resources' blog]

-----

'''August 18, 2015''' - The World Bank Group publishes a post celebrating the April 2015 launch of the World Bank Group Archives' new AtoM site, entitled "An information goldmine: The World Bank Group Archives goes online." Launched as part of the Group's [http://www.worldbank.org/en/topic/opendevelopment Open Development] Initiative and in support of its [http://www.worldbank.org/en/access-to-information Access to Information] Policy, the post says of their new site: "''Created using the Access to Memory open source software, the website facilitates a faster, more efficient, and personalized online service delivery model. The software serves as a catalog that provides basic information about the resources of the Archives, and it is equipped with user-friendly finding aids compliant with the International Standard for Archival Description.''"

* [http://blogs.worldbank.org/voices/information-goldmine-world-bank-group-archives-goes-online See the full post here]
* [https://archivesholdings.worldbank.org/ Explore the World Bank Group Archives Holdings AtoM site]

-----

'''August 4, 2015''' - The [http://royalbcmuseum.bc.ca/ Royal BC Museum] launches a new AtoM-based database for the BC Archives. Launched with a particular focus on the Ida Halpern fonds (see it [http://search-bcarchives.royalbcmuseum.bc.ca/ida-halpern-fonds here]), the accompanying press release noted: "''An improvement on the old BC Archives website for archivists and users alike, AtoM is an ideal platform for the digitized materials in the Ida Halpern fonds (or collection).''" The press release goes on to add, "''AtoM is used by most provincial and national archives, NATO, the World Bank and UNESCO’s archives – extremely good company for the Royal BC Museum to keep. ...As with many of the Royal BC Museum’s recent digital initiatives, AtoM’s debut shows how the Museum and Archives see technology as a smart and easy way to connect today’s public, no matter where they live, with BC’s collective history.''"

* See the new BC Archives AtoM site: http://search-bcarchives.royalbcmuseum.bc.ca
* See the press release [http://royalbcmuseum.bc.ca/assets/2015-08-04-AtoM-launch-Media-Release.pdf here] (PDF)

-----

'''June 8, 2015''' - Simon Fraser University ([http://www.sfu.ca/ SFU]) Archives announces new website content, including a section on digital preservation, describing SFU Archives' use of AtoM and [https://www.archivematica.org Archivematica] for digital preservation and access. From the announcement:

''In 2013-14, the Archives received a three-year SFU University Priority Fund grant to develop a digital repository for archival materials. We're now into Year 3 and moving into production. This page brings together various resources relating to the project, including technical documentation, guidelines and tools, reports and presentations. Content will be added as more documents become available.''

* See the page here: http://www.sfu.ca/archives/digital-repository/dr-overview.html

-----

'''June 4, 2015''' - [http://libraries.dal.ca/collection/archives.html Dalhousie University Archives] announces the availability of the Elisabeth Mann Borgese digital archives, via AtoM. The largest archival digitization project undertaken to date by Dalhousie University, the Borgese collection has already attracted international researchers to Halifax, Nova Scotia and Dalhousie University Archives is now pleased to provide online access to this material for local and distance researchers.
* See the Borgese fonds in AtoM: http://findingaids.library.dal.ca/elisabeth-mann-borgese-fonds
* See the announcement in the AtoM User Forum: https://groups.google.com/d/msg/ica-atom-users/rLa6zr5AsU0/ipKNsxDlfz8J
* See an announcement on the LibVine, a Dalhousie University blog: https://blogs.dal.ca/libraries/2015/05/learn-more-about-a-key-figure-in-ocean-studies-check-out-the-elisabeth-mann-borgese-finding-aid/

-----

'''May 22, 2015''' - [http://catalogue.millsarchive.org/ Mills Archive], based in Reading, UK, has been profiled on the UK's [http://www.nationalarchives.gov.uk/ National Archives] website as a successful case study, after completing a data migration into AtoM and publicly launching earlier this year. On the [https://millsarchive.org/news Mills Archive blog], Liz Bartram notes: "''The reason we are being featured as a case study? Representatives from the National Archives came to visit us and were so impressed that they later approached us to ask if we would write a case study about our new online catalogue system so that other archives can learn from what we have achieved.''"

The National Archives case study comments that "''Using AtoM allows the Mills Archive to provide more information at the collections level and it is a better tool for recording and demonstrating the context and the relationship of records with other material compared to the former catalogue.''" Check it out in the links below:
* Read the Mills Archive blog post: https://millsarchive.org/news/entry/158855/mills-archive-is-featured-on-the-national-archives-website#.VZ-LLvlVhuA
* Read the National Archives case study: http://www.nationalarchives.gov.uk/archives-sector/mills-archive.htm

-----

'''April 30, 2015''' - [http://www.archeion.ca/ Archeion], the Ontario-wide provincial archival portal maintained by the Archives Association of Ontario ([http://aao-archivists.ca AAO]), announces that it now holds over 30,000 descriptions, contributed from institutions all across the Canadian province of Ontario. Announced via a blog entry on the AAO website, the post by Gabrielle Earnshaw and Danielle Robichaud focuses on one of the descriptions that hleped push Archeion over this milestone number: the Henry Nouwen fonds, held by the University of St. Michael’s College in the University of Toronto.

In the post, Earnshaw and Robichaud state: "''As a small archives without a public facing description database, our contribution to Archeion was an important way to reach an audience we may have otherwise missed by relying on our website and more university-focused outreach efforts.''"

* [http://aao-archivists.ca/Archeion/3322735 Henri Nouwen fonds takes Archeion over a new threshold ]

-----

'''April 1, 2015''' - The [https://archivesholdings.worldbank.org/ World Bank Group Archives] publicly launches its new AtoM-based Archives Holdings catalogue. In a publicity post sent to the International Council on Archives' public mailing list, the WBGA notes that "''The Archives of the World Bank Group in Washington, DC is delighted to announce the launch of our Access to Memory (AtoM) site. In support of the World Bank’s commitment to openness, transparency and accountability through its 2010 Access to Information Policy, the site is now the gateway to explore the holdings of the World Bank Group Archives.''" The WBGA team has also offered to to answer questions about its AtoM implementation via email, at [mailto:archives@worldbank.org archives@worldbank.org].

-----

'''March - May 2015''' - A productive and interactive user forum discussion, with contributions from Artefactual, multiple users, and several developers leads to the repair, enhancement, and documentation of AtoM's [http://www.openarchives.org/pmh/ OAI-PMH] module in the [[Releases/Release announcements/Release 2.2#OAI-PMH_exposure_-_returned.21|2.2 release]]. Community development in action!
* See the User forum thread: https://groups.google.com/d/topic/ica-atom-users/6BmOLdLEkPs/discussion
* See the AtoM 2.2 OAI-PMH documentation: https://www.accesstomemory.org/docs/2.2/user-manual/import-export/oai-pmh/

-----

'''March 31, 2015''' - [http://www.memorybc.ca MemoryBC], the portal to archival descriptions in British Columbia maintained by the Archives Association of British Columbia ([http://aabc.ca AABC]), upgrades to AtoM 2.1! As one of the first sites ever to begin using ICA-AtoM 1.0.x-beta in production, we are excited to see MemoryBC upgraded.

-----

'''March 2, 2015''' - [http://archives.mhsc.ca/ MAID], the '''Mennonite Archival Image Database''' goes live for public use after 2 years of collaborative design and development. A project of the Mennonite Historical Society of Canada which includes Mennonite archival partners in British Columbia, Alberta, Saskatchewan, Manitoba, and Ontario, MAID uses AtoM, with some custom features developed by [http://www.peaceworks.ca/ PeaceWorks Technology Solutions] of Waterloo (ON, Canada). News of the launch was published [https://uwaterloo.ca/mennonite-archives-ontario/news/new-online-mennonite-photo-database-shows-future-community here]. In the launch announcement, University of Manitoba archives professor is quoted saying that ''"by using open source code and contributing back to the code base, archives around the world that use AtoM can benefit from the new functionalities created by PeaceWorks for MAID. It is wonderful to see the Canadian Mennonite community working together, embracing digital technologies and contributing to the development of open source technologies."''

* [https://uwaterloo.ca/mennonite-archives-ontario/news/new-online-mennonite-photo-database-shows-future-community Read the launch announcement]

<admonition type="seealso">
Learn more about the custom plugins that PeaceWorks developed for AtoM on our [[Community/Community resources/Development|Community development]] page
</admonition>

-----

'''August 15, 2014''' - City of Coquitlam Archives launches its new AtoM (2.0.1) catalog - QUEST, the City of Coquitlam Archives Online Search Portal - and receives a write-up in the local paper, Tri-City News. See the new site here: http://searcharchives.coquitlam.ca/atom/

[[file:coquitlamArchives-AtoM-2014-08-15.png|center|700px|thumb|Article in the Tri-City News about an AtoM instance]]

-----

'''Spring 2014,''' Pilot Project on AtoM 2.0.1 is launched by the Slovenian Office for Slovenians Abroad. 1250 Archival descriptions, 7 Archival Institutions, and 955 digital objects. View materials in English or Slovenian: [http://www.da-slo.si/da/atom2/index.php/ Digitalni arhiv Slovencev po svetu] supported by ZRC-SAZU, Slovenian Archives in Slovenia, HASA NSW and Slovenian Media House in Australia. Additional support from National Library of Australia.

-----

'''Spring 2013''', [http://archivescollection.anu.edu.au Australian National University Archives] launches their 1800 collections with ICA-AtoM Software. As one of the original beta testers in 2008, the ANU has dedicated a number of years to getting their data entered into ICA-AtoM (1800 collections, over 1200 creators). The database covers two repositories representing 20 kilometers of archives: the Australian National University Archives and the Noel Butlin Archives Centre (Australian business and labour archives), as well as the virtual repository for Pacific Research Archives.

-----

'''Winter 2012''', [http://blogs.ubc.ca/rbscnew/2012/10/12/day-of-digital-archives-our-experience-so-far/ Blogpost] by University of British Columbia's Rare Books and Special Collections Archivist/Librarian Sarah Romkey, about their current work towards integrating ICA-AtoM and Archivematica.

-----

'''Fall 2012''', Blanca Biarge Gallardo releases an [http://www.vidimus.net/wordpress/wp-content/uploads/2014/04/Ica_atom_manual_V02.pdf ICA-AtoM User Manual in Spanish] for [http://www.vidimus.cat Vidimus] a private company specializing in archives and records management. The manual is publicly available as of 2012-10-23.

''Update 2015'' - An updated second edition of the Spanish User Manual is created in April of 2014, and the location is moved on the website. The link above has now been updated.

-----

'''April - May 2012''' Link to [https://groups.google.com/d/topic/ica-atom-users/C_ioACjN4go/discussion User Forum] discussion thread with some examples of ICA-AtoM data-entry practices (and suggestion to start this page).

-----

'''April 2012''' - [http://www.vancouverarchives.ca/2012/04/our-new-online-search Blog post] describing the City of Vancouver Archives' ICA-AtoM installation and migration project.

-----

[http://aao-archivists.ca/archeion-coordinator/173-archeion-workshops-update Update] on training workshops for '''ARCHEION''', the Archivists Association of Ontario portal that is run using AtoM (http://www.archeion.ca/).

-----

'''March 2012''' - ESARBICA newsletter includes an article on an EAD Workshop at Nationaal Archief of the Netherlands with discussion about ICA-AtoM (pgs. 3 & 4) [https://docs.google.com/a/artefactual.com/viewer?a=v&q=cache:FVACAwZTr2wJ:esarbica.org/Jan-Feb%25202012.pdf+&hl=en&gl=us&pid=bl&srcid=ADGEEShhbg1DwUCRcnz1gWMkLCzdwVBSIwFRmN5bVDtt1fUE9ZBOUNuD71lVhjgEDiHad_e9SeTRicJlpmKZpG0D4OaOjkk426-i0Knsx6aiKpzZUUxYGpmsGjbEaVQsF18yPjc2cyYO&sig=AHIEtbRMvUtO2Ok_Y4ihmuZJ4cPJTGTmig&pli=1| View ESARBICA link]

-----

'''July 2012''' - Link to the University of British Columbia's [http://blogs.ubc.ca/rbscnew/2012/07/31/unpacking-the-douglas-coupland-fonds-taxonomies-and-tagging/ Rare Books and Special Collections BLOG] describing the use of ICA-AtoM taxonomies for tagging the Douglas Coupland Fonds

== Example sites ==

* This page lists links to some existing [[Community/Users|AtoM sites]]

== Press releases ==

Link to Dumbarton Oaks Image Collections and Fieldwork Archives Discovery Portal PRESS RELEASE and HELP PAGE explaining how to use ICA-AtoM as a discovery portal, February 2014: [http://www.doaks.org/library-archives/icfa/atom-do-help AtoM@DO]

-----

Link to The Image Collections and Fieldwork Archives Dumbarton Oaks PRESS RELEASE on the ICFA Blog announcing the selection of ICA-AtoM as their Collection Management System (CMS), September 2012: [http://icfadumbartonoaks.wordpress.com/2012/09/05/icfa-picks-a-cms/ ICFA Blog Post about ICA-AtoM Selection]

-----

Link to ARCHEION, the Archivists' Association of Ontario PRESS RELEASE announcing the launch of their portal using ICA-AtoM, December 2011: [[file:archeion_launch2011_thankyou.pdf]] (PDF, 85 KB)

-----

Please revise and add to this page as you like.

* [[Community|Back to the Community landing page]]
* [[Main Page|AtoM wiki home]]

[[Category:Community]]

Releases/Release announcements

2020-07-15T16:39:59Z

JennR:

{{#pagetitle: Release announcements }}

[[Main Page]] > [[Releases]] > Releases/Release announcements

Here are detailed lists of the new features, enhancements, and bug fixes in each ICA-AtoM and AtoM release.

<admonition type="tip">
Looking for information on upcoming releases? Check the [[Releases/Roadmap|Roadmap]] page!
</admonition>

== AtoM (2.x) releases ==

AtoM 2 releases are available on the AtoM website, at: https://www.accesstomemory.org/download/

* [[Releases/Release announcements/Release 2.6|Release 2.6]] (July 14, 2020)
* [[Releases/Release announcements/Release 2.5.4|Release 2.5.4]] (May 5, 2020)
* [[Releases/Release announcements/Release 2.5.3|Release 2.5.3]] (October 30, 2019)
* [[Releases/Release announcements/Release 2.5.2|Release 2.5.2]] (August 29, 2019)
* [[Releases/Release announcements/Release 2.5.1|Release 2.5.1]] (July 3, 2019)
* [[Releases/Release announcements/Release 2.5|Release 2.5]] (May 9, 2019)
* [[Releases/Release announcements/Release 2.4.1|Release 2.4.1]] (November 2, 2018)
* [[Releases/Release announcements/Release 2.4|Release 2.4]] (September 5, 2017)
* [[Releases/Release announcements/Release 2.3.1|Release 2.3.1]] (February 14th, 2017)
* [[Releases/Release announcements/Release 2.3|Release 2.3]] (July 19, 2016)
* [[Releases/Release announcements/Release 2.2.1|Release 2.2.1]] (February 10, 2016)
* [[Releases/Release announcements/Release 2.2|Release 2.2]] (July 10, 2015)
* [[Releases/Release announcements/Release 2.1.2|Release 2.1.2 translation pack]] (February 10, 2015 )
* [[Releases/Release announcements/Release 2.1.1|Release 2.1.1 security upgrade]] (January 28, 2015)
* [[Releases/Release announcements/Release 2.1|Release 2.1.0]] (September 22, 2014)
* [[Releases/Release announcements/Release 2.1.1|Release 2.0.2 security upgrade]] (January 28, 2015)
* [[Releases/Release announcements/Release 2.0.1|Release 2.0.1]] (December 16, 2013)
* [[Releases/Release announcements/Release 2.0.0|Release 2.0.0]] (October 7, 2013)

== ICA-AtoM (1.x) releases ==

For more information about ICA-AtoM, our earlier version of the AtoM software, please visit the ICA-AtoM wiki: https://www.ica-atom.org/doc/Main_Page

* [[Releases/Release announcements/Release 1.4|Release 1.4]] (unscheduled)
* [[Releases/Release announcements/Release 2.1.1|Release 1.3.2 security upgrade]] (January 28, 2015)
* [[Releases/Release announcements/Release 1.3.1|Release 1.3.1]] (May 7, 2013)
* [[Releases/Release announcements/Release 1.3|Release 1.3]] (August 27, 2012)
* [[Releases/Release announcements/Release 1.2.1|Release 1.2.1]] (June 28, 2012)
* [[Releases/Release announcements/Release 1.2|Release 1.2]] (November 29, 2011)
* [[Releases/Release announcements/Release 1.1|Release 1.1]] (November 22, 2010)
* [[Releases/Release announcements/Release 1.0.9-beta|Release 1.0.9-beta]] (May 17, 2010)
* [[Releases/Release announcements/Release 1.0.8-beta|Release 1.0.8-beta]] (November 2, 2009)
* [[Releases/Release announcements/Release 1.0.7-beta|Release 1.0.7-beta]] (June 1, 2009)
* [[Releases/Release announcements/Release 1.0.6-beta|Release 1.0.6-beta]] (April 27, 2009)
* [[Releases/Release announcements/Release 1.0.5-beta|Release 1.0.5-beta]] (March 11, 2009)
* [[Releases/Release announcements/Release 1.0.4-beta|Release 1.0.4-beta]] (November 17, 2008)
* [[Releases/Release announcements/Release 1.0.3-beta|Release 1.0.3-beta]] (October 9, 2008)
* [[Releases/Release announcements/Release 1.0.2-beta|Release 1.0.2-beta]] (August 8, 2008)
* [[Releases/Release announcements/Release 1.0.1-beta|Release 1.0.1-beta]] (July 22, 2008)
* [[Releases/Release announcements/Release 1.0-beta|Release 1.0-beta]] (July 1, 2008)

-----

* [[Releases|Back to Releases]]
* [[Main Page|AtoM wiki home]]

[[Category:Releases]]

Development/Functional testing/Validation tests

2020-07-08T20:56:58Z

JennR: /* Accession record edit template */

{{#pagetitle: Validation tests }}
[[Main Page]] > [[Development]] > [[Development/Functional testing|Functional testing]] > Validation tests

== ISAD(G) template ==

*The following fields in the edit screen have asterisks next to the field labels: identifier, title, dates(s), level of description, extent and medium, name of creator(s).
*Saving a record without an identifier results in the warning "Identifier - This is a mandatory element."
*Saving a record without a title results in the warning "Title - This is a mandatory element."
*Saving a record with none of the date fields (start year, end year or date display) results in the warning "Date(s) - This is a mandatory element."
*Saving a record with one of the date fields (start year, end year or date display) results in no warning about dates.
*Saving a record without extent and medium results in the warning "Extent and medium - This is a mandatory element."
*Saving a record without a creator when no creator has been entered at a higher level of description results in the warning "This archival description, or one of its higher levels, requires at least one creator."
*Saving a record without a creator when a creator has been entered at a higher level of description results in no warning about creator.
*Saving a child record with a creation start year that is earlier than the creation start year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with a creation end year that is later than the creation end year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with a creation start year that is the same as the creation start year for the parent record results in no warning.
*Saving a child record with a creation end year that is the same as the creation end year for the parent record results in no warning.
*Saving a child record with an accumulation start year that is earlier than the accumulation start year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with an accumulation end year that is later than the accumulation end year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with an accumulation start year that is earlier than the creation start year for the parent record results in no warning.
*Saving a child record with an accumulation end year that is later than the creation end year for the parent record results in no warning.
*Saving a child record with an accumulation start year that is the same as the accumulation start year for the parent record results in no warning.
*Saving a child record with an accumulation end year that is the same as the accumulation end year for the parent record results in no warning.
*Saving a child record with a level of description that is at a higher or the same level of aggregation as the parent record results in the warning "Level of description - Value (eg "Fonds") is not consistent with higher levels."
*AtoM is designed to be permissive and it won't check every combination of parent-child. But, validation will take place and warnings will be given in most instances when the level of description being saved does not fit in to the expected hierarchical archival structure.
Test as follows:
**A fonds cannot be a child level of a fonds
**A fonds cannot be a child level of a series
**A fonds cannot be a child level of a file
**A fonds cannot be a child level of an item
**A series cannot be a child level of a file
**A series cannot be a child level of an item
**A file cannot be a child level of a file
**A file cannot be a child level of an item
**An item cannot be a child level of an item

== RAD template ==
*The following fields in the edit screen have asterisks next to the field labels: title proper, level of description, physical description and scope and content. The date field is mandatory at the highest descriptive level, but not at lower levels; therefore, no asterisk appears next to the date entry field.
*Saving a record without a date results in the warning "This archival description requires at least one date."

*Saving a record without a title proper results in the warning "Title - This is a mandatory element"
*Saving a record without a level of description results in the warning "Level of description - This is a mandatory element"
*Saving a record without a physical description results in the warning "Physical description - This is a mandatory element"
*Saving a record without a scope and content results in the warning "Scope and content - This is a mandatory element"

*Saving a child record without a title proper results in the warning "Title - This is a mandatory element"
*Saving a child record without a level of description results in the warning "Level of description - This is a mandatory element"
*Saving a child record without a physical description results in the warning "Physical description - This is a mandatory element"
*Saving a child record without a scope and content results in the warning "Scope and content - This is a mandatory element"

*Saving a child record without a date results in the warning "This archival description requires at least one date."
*Saving a child record with a start date prior to the parent start date results in the warning "Date(s) are not consistent with higher levels"
*Saving a child record with an end date later than the parent end date results in the warning "Date(s) are not consistent with higher levels"

*Saving a child record with a level of description that is at a higher or the same level of aggregation as the parent record results in the warning "Level of description - Value (eg "Fonds") is not consistent with higher levels."
*AtoM is designed to be permissive and it won't check every combination of parent-child. But, validation will take place and warnings will be given in most instances when the level of description being saved does not fit in to the expected hierarchical archival structure.
Test as follows:
**A fonds cannot be a child level of a fonds
**A fonds cannot be a child level of a series
**A fonds cannot be a child level of a file
**A fonds cannot be a child level of an item

== Dublin Core template ==

*The following fields in the edit screen have asterisks next to the field labels: identifier, title, and relation (isLocatedAt).
*Saving a record without an identifier results in the warning "Identifier - This is a mandatory element."
*Saving a record without a title results in the warning "Title - This is a mandatory element."
*Saving a record without a relation (isLocatedAt) results in the warning "Relation (isLocatedAt)-This is a mandatory element for this resource or one of its higher descriptive levels (if part of a collection hierarchy)."

*Child levels created from a parent automatically inherit the relation (isLocatedAt) data.
*If User deletes data from required fields in child level, this results in the warning: "Identifier - This is a mandatory element". "Title - This is a mandatory element." "Relation(isLocatedAt)-This is a mandatory element."

== ISAAR template ==

*The following fields in the edit screen have asterisks next to the field labels: type of entity, authorized form of name, dates of existence and authority record identifier.
*Saving a record without a type of entity results in the warning "Type of entity - This is a mandatory element."
*Saving a record without an authorized form of name results in the warning "Authorized form of name - This is a mandatory element."
*Saving a record without dates of existence results in the warning "Dates of existence - This is a mandatory element."
*Saving a record without an authority record identifier results in the warning "Authority record identifier - This is a mandatory element."
*User is prevented from creating a relationship between an ISAAR record and itself.

== ISDIAH template ==

*The following fields in the edit screen have asterisks next to the field labels: identifier, authorized form of name.
*Saving a record without an identifier results in the warning "Identifier - This is a mandatory element."
*Saving a record without an authorized form of name results in the warning "Authorized form of name - This is a mandatory element."
*Saving a record without at least one of city, country, postal code, region or street address in the contact area results in the warning "Contact information - You must at least include one of the following location or address fields: city, country, postal code, region or street address."

== ISDF template ==

*The following fields in the edit screen have asterisks next to the field labels: type, authorized form of name, description identifier.
*Saving a record without a type results in the warning "Type - This is a mandatory element."
*Saving a record without an authorized form of name results in the warning "Authorized form of name - This is a mandatory element."
*Saving a record without a function description identifier results in the warning "Description identifier - This is a mandatory element."
*User is prevented from creating a relationship between an ISDF record and itself.

== Term template ==
*Cannot select a broad term that is the same as a the current term
*Cannot select a broad term that is a narrow term of the current term
*Cannot select a related term that is the same as the current term
*Cannot select a related term that is a broad term of the current term
*Cannot select a related term that is a narrow term of the current term

== User edit template ==
*The following fields in the edit screen have asterisks next to the field labels: username, email.
*Saving a record without a username results in the warning "Required" appearing above the field and the record does not save.
*Saving a record without an email results in the warning "Required" appearing above the field and the record does not save.
*Saving a record without a password results in the warning "Required" appearing above the field and the record does not save.
*Saving a record without confirming password results in the warning "Your password confirmation did not match your password" and the record does not save.

== Accession record edit template ==
*The following fields in the edit screen have asterisks next to the field labels: acquisition date, immediate source of acquisition, location information, accession number. The record can be saved, even with a warning.
*Saving a record without an acquisition date results in the warning "Acquisition date- This is a mandatory element"
*Saving a record without a source of acquisition results in the warning "Source of acquisition - This is a mandatory element"
*Saving a record without location information results in the warning "Location information - This is a mandatory element"

[[Category:Development documentation]]
__NOTOC__

Development/Functional testing/Validation tests

2020-07-08T20:56:17Z

JennR: /* User edit template */

{{#pagetitle: Validation tests }}
[[Main Page]] > [[Development]] > [[Development/Functional testing|Functional testing]] > Validation tests

== ISAD(G) template ==

*The following fields in the edit screen have asterisks next to the field labels: identifier, title, dates(s), level of description, extent and medium, name of creator(s).
*Saving a record without an identifier results in the warning "Identifier - This is a mandatory element."
*Saving a record without a title results in the warning "Title - This is a mandatory element."
*Saving a record with none of the date fields (start year, end year or date display) results in the warning "Date(s) - This is a mandatory element."
*Saving a record with one of the date fields (start year, end year or date display) results in no warning about dates.
*Saving a record without extent and medium results in the warning "Extent and medium - This is a mandatory element."
*Saving a record without a creator when no creator has been entered at a higher level of description results in the warning "This archival description, or one of its higher levels, requires at least one creator."
*Saving a record without a creator when a creator has been entered at a higher level of description results in no warning about creator.
*Saving a child record with a creation start year that is earlier than the creation start year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with a creation end year that is later than the creation end year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with a creation start year that is the same as the creation start year for the parent record results in no warning.
*Saving a child record with a creation end year that is the same as the creation end year for the parent record results in no warning.
*Saving a child record with an accumulation start year that is earlier than the accumulation start year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with an accumulation end year that is later than the accumulation end year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with an accumulation start year that is earlier than the creation start year for the parent record results in no warning.
*Saving a child record with an accumulation end year that is later than the creation end year for the parent record results in no warning.
*Saving a child record with an accumulation start year that is the same as the accumulation start year for the parent record results in no warning.
*Saving a child record with an accumulation end year that is the same as the accumulation end year for the parent record results in no warning.
*Saving a child record with a level of description that is at a higher or the same level of aggregation as the parent record results in the warning "Level of description - Value (eg "Fonds") is not consistent with higher levels."
*AtoM is designed to be permissive and it won't check every combination of parent-child. But, validation will take place and warnings will be given in most instances when the level of description being saved does not fit in to the expected hierarchical archival structure.
Test as follows:
**A fonds cannot be a child level of a fonds
**A fonds cannot be a child level of a series
**A fonds cannot be a child level of a file
**A fonds cannot be a child level of an item
**A series cannot be a child level of a file
**A series cannot be a child level of an item
**A file cannot be a child level of a file
**A file cannot be a child level of an item
**An item cannot be a child level of an item

== RAD template ==
*The following fields in the edit screen have asterisks next to the field labels: title proper, level of description, physical description and scope and content. The date field is mandatory at the highest descriptive level, but not at lower levels; therefore, no asterisk appears next to the date entry field.
*Saving a record without a date results in the warning "This archival description requires at least one date."

*Saving a record without a title proper results in the warning "Title - This is a mandatory element"
*Saving a record without a level of description results in the warning "Level of description - This is a mandatory element"
*Saving a record without a physical description results in the warning "Physical description - This is a mandatory element"
*Saving a record without a scope and content results in the warning "Scope and content - This is a mandatory element"

*Saving a child record without a title proper results in the warning "Title - This is a mandatory element"
*Saving a child record without a level of description results in the warning "Level of description - This is a mandatory element"
*Saving a child record without a physical description results in the warning "Physical description - This is a mandatory element"
*Saving a child record without a scope and content results in the warning "Scope and content - This is a mandatory element"

*Saving a child record without a date results in the warning "This archival description requires at least one date."
*Saving a child record with a start date prior to the parent start date results in the warning "Date(s) are not consistent with higher levels"
*Saving a child record with an end date later than the parent end date results in the warning "Date(s) are not consistent with higher levels"

*Saving a child record with a level of description that is at a higher or the same level of aggregation as the parent record results in the warning "Level of description - Value (eg "Fonds") is not consistent with higher levels."
*AtoM is designed to be permissive and it won't check every combination of parent-child. But, validation will take place and warnings will be given in most instances when the level of description being saved does not fit in to the expected hierarchical archival structure.
Test as follows:
**A fonds cannot be a child level of a fonds
**A fonds cannot be a child level of a series
**A fonds cannot be a child level of a file
**A fonds cannot be a child level of an item

== Dublin Core template ==

*The following fields in the edit screen have asterisks next to the field labels: identifier, title, and relation (isLocatedAt).
*Saving a record without an identifier results in the warning "Identifier - This is a mandatory element."
*Saving a record without a title results in the warning "Title - This is a mandatory element."
*Saving a record without a relation (isLocatedAt) results in the warning "Relation (isLocatedAt)-This is a mandatory element for this resource or one of its higher descriptive levels (if part of a collection hierarchy)."

*Child levels created from a parent automatically inherit the relation (isLocatedAt) data.
*If User deletes data from required fields in child level, this results in the warning: "Identifier - This is a mandatory element". "Title - This is a mandatory element." "Relation(isLocatedAt)-This is a mandatory element."

== ISAAR template ==

*The following fields in the edit screen have asterisks next to the field labels: type of entity, authorized form of name, dates of existence and authority record identifier.
*Saving a record without a type of entity results in the warning "Type of entity - This is a mandatory element."
*Saving a record without an authorized form of name results in the warning "Authorized form of name - This is a mandatory element."
*Saving a record without dates of existence results in the warning "Dates of existence - This is a mandatory element."
*Saving a record without an authority record identifier results in the warning "Authority record identifier - This is a mandatory element."
*User is prevented from creating a relationship between an ISAAR record and itself.

== ISDIAH template ==

*The following fields in the edit screen have asterisks next to the field labels: identifier, authorized form of name.
*Saving a record without an identifier results in the warning "Identifier - This is a mandatory element."
*Saving a record without an authorized form of name results in the warning "Authorized form of name - This is a mandatory element."
*Saving a record without at least one of city, country, postal code, region or street address in the contact area results in the warning "Contact information - You must at least include one of the following location or address fields: city, country, postal code, region or street address."

== ISDF template ==

*The following fields in the edit screen have asterisks next to the field labels: type, authorized form of name, description identifier.
*Saving a record without a type results in the warning "Type - This is a mandatory element."
*Saving a record without an authorized form of name results in the warning "Authorized form of name - This is a mandatory element."
*Saving a record without a function description identifier results in the warning "Description identifier - This is a mandatory element."
*User is prevented from creating a relationship between an ISDF record and itself.

== Term template ==
*Cannot select a broad term that is the same as a the current term
*Cannot select a broad term that is a narrow term of the current term
*Cannot select a related term that is the same as the current term
*Cannot select a related term that is a broad term of the current term
*Cannot select a related term that is a narrow term of the current term

== User edit template ==
*The following fields in the edit screen have asterisks next to the field labels: username, email.
*Saving a record without a username results in the warning "Required" appearing above the field and the record does not save.
*Saving a record without an email results in the warning "Required" appearing above the field and the record does not save.
*Saving a record without a password results in the warning "Required" appearing above the field and the record does not save.
*Saving a record without confirming password results in the warning "Your password confirmation did not match your password" and the record does not save.

== Accession record edit template ==
*The following fields in the edit screen have asterisks next to the field labels: acquisition date, immediate source of acquisition, location information. The record can be saved, even with a warning.
*Saving a record without an acquisition date results in the warning "Acquisition date- This is a mandatory element"
*Saving a record without a source of acquisition results in the warning "Source of acquisition - This is a mandatory element"
*Saving a record without location information results in the warning "Location information - This is a mandatory element"

[[Category:Development documentation]]
__NOTOC__

Development/Functional testing/Validation tests

2020-07-08T20:50:24Z

JennR: /* ISDIAH template */

{{#pagetitle: Validation tests }}
[[Main Page]] > [[Development]] > [[Development/Functional testing|Functional testing]] > Validation tests

== ISAD(G) template ==

*The following fields in the edit screen have asterisks next to the field labels: identifier, title, dates(s), level of description, extent and medium, name of creator(s).
*Saving a record without an identifier results in the warning "Identifier - This is a mandatory element."
*Saving a record without a title results in the warning "Title - This is a mandatory element."
*Saving a record with none of the date fields (start year, end year or date display) results in the warning "Date(s) - This is a mandatory element."
*Saving a record with one of the date fields (start year, end year or date display) results in no warning about dates.
*Saving a record without extent and medium results in the warning "Extent and medium - This is a mandatory element."
*Saving a record without a creator when no creator has been entered at a higher level of description results in the warning "This archival description, or one of its higher levels, requires at least one creator."
*Saving a record without a creator when a creator has been entered at a higher level of description results in no warning about creator.
*Saving a child record with a creation start year that is earlier than the creation start year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with a creation end year that is later than the creation end year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with a creation start year that is the same as the creation start year for the parent record results in no warning.
*Saving a child record with a creation end year that is the same as the creation end year for the parent record results in no warning.
*Saving a child record with an accumulation start year that is earlier than the accumulation start year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with an accumulation end year that is later than the accumulation end year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with an accumulation start year that is earlier than the creation start year for the parent record results in no warning.
*Saving a child record with an accumulation end year that is later than the creation end year for the parent record results in no warning.
*Saving a child record with an accumulation start year that is the same as the accumulation start year for the parent record results in no warning.
*Saving a child record with an accumulation end year that is the same as the accumulation end year for the parent record results in no warning.
*Saving a child record with a level of description that is at a higher or the same level of aggregation as the parent record results in the warning "Level of description - Value (eg "Fonds") is not consistent with higher levels."
*AtoM is designed to be permissive and it won't check every combination of parent-child. But, validation will take place and warnings will be given in most instances when the level of description being saved does not fit in to the expected hierarchical archival structure.
Test as follows:
**A fonds cannot be a child level of a fonds
**A fonds cannot be a child level of a series
**A fonds cannot be a child level of a file
**A fonds cannot be a child level of an item
**A series cannot be a child level of a file
**A series cannot be a child level of an item
**A file cannot be a child level of a file
**A file cannot be a child level of an item
**An item cannot be a child level of an item

== RAD template ==
*The following fields in the edit screen have asterisks next to the field labels: title proper, level of description, physical description and scope and content. The date field is mandatory at the highest descriptive level, but not at lower levels; therefore, no asterisk appears next to the date entry field.
*Saving a record without a date results in the warning "This archival description requires at least one date."

*Saving a record without a title proper results in the warning "Title - This is a mandatory element"
*Saving a record without a level of description results in the warning "Level of description - This is a mandatory element"
*Saving a record without a physical description results in the warning "Physical description - This is a mandatory element"
*Saving a record without a scope and content results in the warning "Scope and content - This is a mandatory element"

*Saving a child record without a title proper results in the warning "Title - This is a mandatory element"
*Saving a child record without a level of description results in the warning "Level of description - This is a mandatory element"
*Saving a child record without a physical description results in the warning "Physical description - This is a mandatory element"
*Saving a child record without a scope and content results in the warning "Scope and content - This is a mandatory element"

*Saving a child record without a date results in the warning "This archival description requires at least one date."
*Saving a child record with a start date prior to the parent start date results in the warning "Date(s) are not consistent with higher levels"
*Saving a child record with an end date later than the parent end date results in the warning "Date(s) are not consistent with higher levels"

*Saving a child record with a level of description that is at a higher or the same level of aggregation as the parent record results in the warning "Level of description - Value (eg "Fonds") is not consistent with higher levels."
*AtoM is designed to be permissive and it won't check every combination of parent-child. But, validation will take place and warnings will be given in most instances when the level of description being saved does not fit in to the expected hierarchical archival structure.
Test as follows:
**A fonds cannot be a child level of a fonds
**A fonds cannot be a child level of a series
**A fonds cannot be a child level of a file
**A fonds cannot be a child level of an item

== Dublin Core template ==

*The following fields in the edit screen have asterisks next to the field labels: identifier, title, and relation (isLocatedAt).
*Saving a record without an identifier results in the warning "Identifier - This is a mandatory element."
*Saving a record without a title results in the warning "Title - This is a mandatory element."
*Saving a record without a relation (isLocatedAt) results in the warning "Relation (isLocatedAt)-This is a mandatory element for this resource or one of its higher descriptive levels (if part of a collection hierarchy)."

*Child levels created from a parent automatically inherit the relation (isLocatedAt) data.
*If User deletes data from required fields in child level, this results in the warning: "Identifier - This is a mandatory element". "Title - This is a mandatory element." "Relation(isLocatedAt)-This is a mandatory element."

== ISAAR template ==

*The following fields in the edit screen have asterisks next to the field labels: type of entity, authorized form of name, dates of existence and authority record identifier.
*Saving a record without a type of entity results in the warning "Type of entity - This is a mandatory element."
*Saving a record without an authorized form of name results in the warning "Authorized form of name - This is a mandatory element."
*Saving a record without dates of existence results in the warning "Dates of existence - This is a mandatory element."
*Saving a record without an authority record identifier results in the warning "Authority record identifier - This is a mandatory element."
*User is prevented from creating a relationship between an ISAAR record and itself.

== ISDIAH template ==

*The following fields in the edit screen have asterisks next to the field labels: identifier, authorized form of name.
*Saving a record without an identifier results in the warning "Identifier - This is a mandatory element."
*Saving a record without an authorized form of name results in the warning "Authorized form of name - This is a mandatory element."
*Saving a record without at least one of city, country, postal code, region or street address in the contact area results in the warning "Contact information - You must at least include one of the following location or address fields: city, country, postal code, region or street address."

== ISDF template ==

*The following fields in the edit screen have asterisks next to the field labels: type, authorized form of name, description identifier.
*Saving a record without a type results in the warning "Type - This is a mandatory element."
*Saving a record without an authorized form of name results in the warning "Authorized form of name - This is a mandatory element."
*Saving a record without a function description identifier results in the warning "Description identifier - This is a mandatory element."
*User is prevented from creating a relationship between an ISDF record and itself.

== Term template ==
*Cannot select a broad term that is the same as a the current term
*Cannot select a broad term that is a narrow term of the current term
*Cannot select a related term that is the same as the current term
*Cannot select a related term that is a broad term of the current term
*Cannot select a related term that is a narrow term of the current term

== User edit template ==
*The following fields in the edit screen have asterisks next to the field labels: username, email, password, confirm password
*Saving a record without a username results in the warning "Required" appearing above the field and the record does not save.
*Saving a record without an email results in the warning "Required" appearing above the field and the record does not save.
*Saving a record without a password results in the warning "Required" appearing above the field and the record does not save.
*Saving a record without confirming password results in the warning "Your password confirmation did not match your password" and the record does not save.

== Accession record edit template ==
*The following fields in the edit screen have asterisks next to the field labels: acquisition date, immediate source of acquisition, location information. The record can be saved, even with a warning.
*Saving a record without an acquisition date results in the warning "Acquisition date- This is a mandatory element"
*Saving a record without a source of acquisition results in the warning "Source of acquisition - This is a mandatory element"
*Saving a record without location information results in the warning "Location information - This is a mandatory element"

[[Category:Development documentation]]
__NOTOC__

Development/Functional testing/Validation tests

2020-07-08T20:48:59Z

JennR: /* ISAAR template */

{{#pagetitle: Validation tests }}
[[Main Page]] > [[Development]] > [[Development/Functional testing|Functional testing]] > Validation tests

== ISAD(G) template ==

*The following fields in the edit screen have asterisks next to the field labels: identifier, title, dates(s), level of description, extent and medium, name of creator(s).
*Saving a record without an identifier results in the warning "Identifier - This is a mandatory element."
*Saving a record without a title results in the warning "Title - This is a mandatory element."
*Saving a record with none of the date fields (start year, end year or date display) results in the warning "Date(s) - This is a mandatory element."
*Saving a record with one of the date fields (start year, end year or date display) results in no warning about dates.
*Saving a record without extent and medium results in the warning "Extent and medium - This is a mandatory element."
*Saving a record without a creator when no creator has been entered at a higher level of description results in the warning "This archival description, or one of its higher levels, requires at least one creator."
*Saving a record without a creator when a creator has been entered at a higher level of description results in no warning about creator.
*Saving a child record with a creation start year that is earlier than the creation start year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with a creation end year that is later than the creation end year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with a creation start year that is the same as the creation start year for the parent record results in no warning.
*Saving a child record with a creation end year that is the same as the creation end year for the parent record results in no warning.
*Saving a child record with an accumulation start year that is earlier than the accumulation start year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with an accumulation end year that is later than the accumulation end year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with an accumulation start year that is earlier than the creation start year for the parent record results in no warning.
*Saving a child record with an accumulation end year that is later than the creation end year for the parent record results in no warning.
*Saving a child record with an accumulation start year that is the same as the accumulation start year for the parent record results in no warning.
*Saving a child record with an accumulation end year that is the same as the accumulation end year for the parent record results in no warning.
*Saving a child record with a level of description that is at a higher or the same level of aggregation as the parent record results in the warning "Level of description - Value (eg "Fonds") is not consistent with higher levels."
*AtoM is designed to be permissive and it won't check every combination of parent-child. But, validation will take place and warnings will be given in most instances when the level of description being saved does not fit in to the expected hierarchical archival structure.
Test as follows:
**A fonds cannot be a child level of a fonds
**A fonds cannot be a child level of a series
**A fonds cannot be a child level of a file
**A fonds cannot be a child level of an item
**A series cannot be a child level of a file
**A series cannot be a child level of an item
**A file cannot be a child level of a file
**A file cannot be a child level of an item
**An item cannot be a child level of an item

== RAD template ==
*The following fields in the edit screen have asterisks next to the field labels: title proper, level of description, physical description and scope and content. The date field is mandatory at the highest descriptive level, but not at lower levels; therefore, no asterisk appears next to the date entry field.
*Saving a record without a date results in the warning "This archival description requires at least one date."

*Saving a record without a title proper results in the warning "Title - This is a mandatory element"
*Saving a record without a level of description results in the warning "Level of description - This is a mandatory element"
*Saving a record without a physical description results in the warning "Physical description - This is a mandatory element"
*Saving a record without a scope and content results in the warning "Scope and content - This is a mandatory element"

*Saving a child record without a title proper results in the warning "Title - This is a mandatory element"
*Saving a child record without a level of description results in the warning "Level of description - This is a mandatory element"
*Saving a child record without a physical description results in the warning "Physical description - This is a mandatory element"
*Saving a child record without a scope and content results in the warning "Scope and content - This is a mandatory element"

*Saving a child record without a date results in the warning "This archival description requires at least one date."
*Saving a child record with a start date prior to the parent start date results in the warning "Date(s) are not consistent with higher levels"
*Saving a child record with an end date later than the parent end date results in the warning "Date(s) are not consistent with higher levels"

*Saving a child record with a level of description that is at a higher or the same level of aggregation as the parent record results in the warning "Level of description - Value (eg "Fonds") is not consistent with higher levels."
*AtoM is designed to be permissive and it won't check every combination of parent-child. But, validation will take place and warnings will be given in most instances when the level of description being saved does not fit in to the expected hierarchical archival structure.
Test as follows:
**A fonds cannot be a child level of a fonds
**A fonds cannot be a child level of a series
**A fonds cannot be a child level of a file
**A fonds cannot be a child level of an item

== Dublin Core template ==

*The following fields in the edit screen have asterisks next to the field labels: identifier, title, and relation (isLocatedAt).
*Saving a record without an identifier results in the warning "Identifier - This is a mandatory element."
*Saving a record without a title results in the warning "Title - This is a mandatory element."
*Saving a record without a relation (isLocatedAt) results in the warning "Relation (isLocatedAt)-This is a mandatory element for this resource or one of its higher descriptive levels (if part of a collection hierarchy)."

*Child levels created from a parent automatically inherit the relation (isLocatedAt) data.
*If User deletes data from required fields in child level, this results in the warning: "Identifier - This is a mandatory element". "Title - This is a mandatory element." "Relation(isLocatedAt)-This is a mandatory element."

== ISAAR template ==

*The following fields in the edit screen have asterisks next to the field labels: type of entity, authorized form of name, dates of existence and authority record identifier.
*Saving a record without a type of entity results in the warning "Type of entity - This is a mandatory element."
*Saving a record without an authorized form of name results in the warning "Authorized form of name - This is a mandatory element."
*Saving a record without dates of existence results in the warning "Dates of existence - This is a mandatory element."
*Saving a record without an authority record identifier results in the warning "Authority record identifier - This is a mandatory element."
*User is prevented from creating a relationship between an ISAAR record and itself.

== ISDIAH template ==

*The following fields in the edit screen have asterisks next to the field labels: identifier, authorized form of name, contact information.
*Saving a record without an identifier results in the warning "Identifier - This is a mandatory element."
*Saving a record without an authorized form of name results in the warning "Authorized form of name - This is a mandatory element."
*Saving a record without at least one of city, country, postal code, region or street address results in the warning "Contact information - You must at least include one of the following location or address fields: city, country, postal code, region or street address."

== ISDF template ==

*The following fields in the edit screen have asterisks next to the field labels: type, authorized form of name, description identifier.
*Saving a record without a type results in the warning "Type - This is a mandatory element."
*Saving a record without an authorized form of name results in the warning "Authorized form of name - This is a mandatory element."
*Saving a record without a function description identifier results in the warning "Description identifier - This is a mandatory element."
*User is prevented from creating a relationship between an ISDF record and itself.

== Term template ==
*Cannot select a broad term that is the same as a the current term
*Cannot select a broad term that is a narrow term of the current term
*Cannot select a related term that is the same as the current term
*Cannot select a related term that is a broad term of the current term
*Cannot select a related term that is a narrow term of the current term

== User edit template ==
*The following fields in the edit screen have asterisks next to the field labels: username, email, password, confirm password
*Saving a record without a username results in the warning "Required" appearing above the field and the record does not save.
*Saving a record without an email results in the warning "Required" appearing above the field and the record does not save.
*Saving a record without a password results in the warning "Required" appearing above the field and the record does not save.
*Saving a record without confirming password results in the warning "Your password confirmation did not match your password" and the record does not save.

== Accession record edit template ==
*The following fields in the edit screen have asterisks next to the field labels: acquisition date, immediate source of acquisition, location information. The record can be saved, even with a warning.
*Saving a record without an acquisition date results in the warning "Acquisition date- This is a mandatory element"
*Saving a record without a source of acquisition results in the warning "Source of acquisition - This is a mandatory element"
*Saving a record without location information results in the warning "Location information - This is a mandatory element"

[[Category:Development documentation]]
__NOTOC__

Development/Functional testing/Validation tests

2020-07-08T20:46:53Z

JennR: /* Dublin Core template */

{{#pagetitle: Validation tests }}
[[Main Page]] > [[Development]] > [[Development/Functional testing|Functional testing]] > Validation tests

== ISAD(G) template ==

*The following fields in the edit screen have asterisks next to the field labels: identifier, title, dates(s), level of description, extent and medium, name of creator(s).
*Saving a record without an identifier results in the warning "Identifier - This is a mandatory element."
*Saving a record without a title results in the warning "Title - This is a mandatory element."
*Saving a record with none of the date fields (start year, end year or date display) results in the warning "Date(s) - This is a mandatory element."
*Saving a record with one of the date fields (start year, end year or date display) results in no warning about dates.
*Saving a record without extent and medium results in the warning "Extent and medium - This is a mandatory element."
*Saving a record without a creator when no creator has been entered at a higher level of description results in the warning "This archival description, or one of its higher levels, requires at least one creator."
*Saving a record without a creator when a creator has been entered at a higher level of description results in no warning about creator.
*Saving a child record with a creation start year that is earlier than the creation start year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with a creation end year that is later than the creation end year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with a creation start year that is the same as the creation start year for the parent record results in no warning.
*Saving a child record with a creation end year that is the same as the creation end year for the parent record results in no warning.
*Saving a child record with an accumulation start year that is earlier than the accumulation start year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with an accumulation end year that is later than the accumulation end year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with an accumulation start year that is earlier than the creation start year for the parent record results in no warning.
*Saving a child record with an accumulation end year that is later than the creation end year for the parent record results in no warning.
*Saving a child record with an accumulation start year that is the same as the accumulation start year for the parent record results in no warning.
*Saving a child record with an accumulation end year that is the same as the accumulation end year for the parent record results in no warning.
*Saving a child record with a level of description that is at a higher or the same level of aggregation as the parent record results in the warning "Level of description - Value (eg "Fonds") is not consistent with higher levels."
*AtoM is designed to be permissive and it won't check every combination of parent-child. But, validation will take place and warnings will be given in most instances when the level of description being saved does not fit in to the expected hierarchical archival structure.
Test as follows:
**A fonds cannot be a child level of a fonds
**A fonds cannot be a child level of a series
**A fonds cannot be a child level of a file
**A fonds cannot be a child level of an item
**A series cannot be a child level of a file
**A series cannot be a child level of an item
**A file cannot be a child level of a file
**A file cannot be a child level of an item
**An item cannot be a child level of an item

== RAD template ==
*The following fields in the edit screen have asterisks next to the field labels: title proper, level of description, physical description and scope and content. The date field is mandatory at the highest descriptive level, but not at lower levels; therefore, no asterisk appears next to the date entry field.
*Saving a record without a date results in the warning "This archival description requires at least one date."

*Saving a record without a title proper results in the warning "Title - This is a mandatory element"
*Saving a record without a level of description results in the warning "Level of description - This is a mandatory element"
*Saving a record without a physical description results in the warning "Physical description - This is a mandatory element"
*Saving a record without a scope and content results in the warning "Scope and content - This is a mandatory element"

*Saving a child record without a title proper results in the warning "Title - This is a mandatory element"
*Saving a child record without a level of description results in the warning "Level of description - This is a mandatory element"
*Saving a child record without a physical description results in the warning "Physical description - This is a mandatory element"
*Saving a child record without a scope and content results in the warning "Scope and content - This is a mandatory element"

*Saving a child record without a date results in the warning "This archival description requires at least one date."
*Saving a child record with a start date prior to the parent start date results in the warning "Date(s) are not consistent with higher levels"
*Saving a child record with an end date later than the parent end date results in the warning "Date(s) are not consistent with higher levels"

*Saving a child record with a level of description that is at a higher or the same level of aggregation as the parent record results in the warning "Level of description - Value (eg "Fonds") is not consistent with higher levels."
*AtoM is designed to be permissive and it won't check every combination of parent-child. But, validation will take place and warnings will be given in most instances when the level of description being saved does not fit in to the expected hierarchical archival structure.
Test as follows:
**A fonds cannot be a child level of a fonds
**A fonds cannot be a child level of a series
**A fonds cannot be a child level of a file
**A fonds cannot be a child level of an item

== Dublin Core template ==

*The following fields in the edit screen have asterisks next to the field labels: identifier, title, and relation (isLocatedAt).
*Saving a record without an identifier results in the warning "Identifier - This is a mandatory element."
*Saving a record without a title results in the warning "Title - This is a mandatory element."
*Saving a record without a relation (isLocatedAt) results in the warning "Relation (isLocatedAt)-This is a mandatory element for this resource or one of its higher descriptive levels (if part of a collection hierarchy)."

*Child levels created from a parent automatically inherit the relation (isLocatedAt) data.
*If User deletes data from required fields in child level, this results in the warning: "Identifier - This is a mandatory element". "Title - This is a mandatory element." "Relation(isLocatedAt)-This is a mandatory element."

== ISAAR template ==

*The following fields in the edit screen have asterisks next to the field labels: type of entity, authorized form of name, dates of existence and description identifier.
*Saving a record without a type of entity results in the warning "Type of entity - This is a mandatory element."
*Saving a record without an authorized form of name results in the warning "Authorized form of name - This is a mandatory element."
*Saving a record without dates of existence results in the warning "Dates of existence - This is a mandatory element."
*Saving a record without an authority record identifier results in the warning "Description identifier - This is a mandatory element."
*User is prevented from creating a relationship between an ISAAR record and itself.

== ISDIAH template ==

*The following fields in the edit screen have asterisks next to the field labels: identifier, authorized form of name, contact information.
*Saving a record without an identifier results in the warning "Identifier - This is a mandatory element."
*Saving a record without an authorized form of name results in the warning "Authorized form of name - This is a mandatory element."
*Saving a record without at least one of city, country, postal code, region or street address results in the warning "Contact information - You must at least include one of the following location or address fields: city, country, postal code, region or street address."

== ISDF template ==

*The following fields in the edit screen have asterisks next to the field labels: type, authorized form of name, description identifier.
*Saving a record without a type results in the warning "Type - This is a mandatory element."
*Saving a record without an authorized form of name results in the warning "Authorized form of name - This is a mandatory element."
*Saving a record without a function description identifier results in the warning "Description identifier - This is a mandatory element."
*User is prevented from creating a relationship between an ISDF record and itself.

== Term template ==
*Cannot select a broad term that is the same as a the current term
*Cannot select a broad term that is a narrow term of the current term
*Cannot select a related term that is the same as the current term
*Cannot select a related term that is a broad term of the current term
*Cannot select a related term that is a narrow term of the current term

== User edit template ==
*The following fields in the edit screen have asterisks next to the field labels: username, email, password, confirm password
*Saving a record without a username results in the warning "Required" appearing above the field and the record does not save.
*Saving a record without an email results in the warning "Required" appearing above the field and the record does not save.
*Saving a record without a password results in the warning "Required" appearing above the field and the record does not save.
*Saving a record without confirming password results in the warning "Your password confirmation did not match your password" and the record does not save.

== Accession record edit template ==
*The following fields in the edit screen have asterisks next to the field labels: acquisition date, immediate source of acquisition, location information. The record can be saved, even with a warning.
*Saving a record without an acquisition date results in the warning "Acquisition date- This is a mandatory element"
*Saving a record without a source of acquisition results in the warning "Source of acquisition - This is a mandatory element"
*Saving a record without location information results in the warning "Location information - This is a mandatory element"

[[Category:Development documentation]]
__NOTOC__

Development/Functional testing/Validation tests

2020-07-07T23:54:54Z

JennR: /* RAD template */

{{#pagetitle: Validation tests }}
[[Main Page]] > [[Development]] > [[Development/Functional testing|Functional testing]] > Validation tests

== ISAD(G) template ==

*The following fields in the edit screen have asterisks next to the field labels: identifier, title, dates(s), level of description, extent and medium, name of creator(s).
*Saving a record without an identifier results in the warning "Identifier - This is a mandatory element."
*Saving a record without a title results in the warning "Title - This is a mandatory element."
*Saving a record with none of the date fields (start year, end year or date display) results in the warning "Date(s) - This is a mandatory element."
*Saving a record with one of the date fields (start year, end year or date display) results in no warning about dates.
*Saving a record without extent and medium results in the warning "Extent and medium - This is a mandatory element."
*Saving a record without a creator when no creator has been entered at a higher level of description results in the warning "This archival description, or one of its higher levels, requires at least one creator."
*Saving a record without a creator when a creator has been entered at a higher level of description results in no warning about creator.
*Saving a child record with a creation start year that is earlier than the creation start year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with a creation end year that is later than the creation end year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with a creation start year that is the same as the creation start year for the parent record results in no warning.
*Saving a child record with a creation end year that is the same as the creation end year for the parent record results in no warning.
*Saving a child record with an accumulation start year that is earlier than the accumulation start year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with an accumulation end year that is later than the accumulation end year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with an accumulation start year that is earlier than the creation start year for the parent record results in no warning.
*Saving a child record with an accumulation end year that is later than the creation end year for the parent record results in no warning.
*Saving a child record with an accumulation start year that is the same as the accumulation start year for the parent record results in no warning.
*Saving a child record with an accumulation end year that is the same as the accumulation end year for the parent record results in no warning.
*Saving a child record with a level of description that is at a higher or the same level of aggregation as the parent record results in the warning "Level of description - Value (eg "Fonds") is not consistent with higher levels."
*AtoM is designed to be permissive and it won't check every combination of parent-child. But, validation will take place and warnings will be given in most instances when the level of description being saved does not fit in to the expected hierarchical archival structure.
Test as follows:
**A fonds cannot be a child level of a fonds
**A fonds cannot be a child level of a series
**A fonds cannot be a child level of a file
**A fonds cannot be a child level of an item
**A series cannot be a child level of a file
**A series cannot be a child level of an item
**A file cannot be a child level of a file
**A file cannot be a child level of an item
**An item cannot be a child level of an item

== RAD template ==
*The following fields in the edit screen have asterisks next to the field labels: title proper, level of description, physical description and scope and content. The date field is mandatory at the highest descriptive level, but not at lower levels; therefore, no asterisk appears next to the date entry field.
*Saving a record without a date results in the warning "This archival description requires at least one date."

*Saving a record without a title proper results in the warning "Title - This is a mandatory element"
*Saving a record without a level of description results in the warning "Level of description - This is a mandatory element"
*Saving a record without a physical description results in the warning "Physical description - This is a mandatory element"
*Saving a record without a scope and content results in the warning "Scope and content - This is a mandatory element"

*Saving a child record without a title proper results in the warning "Title - This is a mandatory element"
*Saving a child record without a level of description results in the warning "Level of description - This is a mandatory element"
*Saving a child record without a physical description results in the warning "Physical description - This is a mandatory element"
*Saving a child record without a scope and content results in the warning "Scope and content - This is a mandatory element"

*Saving a child record without a date results in the warning "This archival description requires at least one date."
*Saving a child record with a start date prior to the parent start date results in the warning "Date(s) are not consistent with higher levels"
*Saving a child record with an end date later than the parent end date results in the warning "Date(s) are not consistent with higher levels"

*Saving a child record with a level of description that is at a higher or the same level of aggregation as the parent record results in the warning "Level of description - Value (eg "Fonds") is not consistent with higher levels."
*AtoM is designed to be permissive and it won't check every combination of parent-child. But, validation will take place and warnings will be given in most instances when the level of description being saved does not fit in to the expected hierarchical archival structure.
Test as follows:
**A fonds cannot be a child level of a fonds
**A fonds cannot be a child level of a series
**A fonds cannot be a child level of a file
**A fonds cannot be a child level of an item

== Dublin Core template ==

*The following fields in the edit screen have asterisks next to the field labels: identifier, title, and relation (isLocatedAt).
*Saving a record without an identifier results in the warning "Identifier - This is a mandatory element for this resource or one of its higher descriptive levels (if part of a collection hierarchy)." Issue 2340
*Saving a record without a title results in the warning "Title - This is a mandatory element for this resource or one of its higher descriptive levels (if part of a collection hierarchy)."
*Saving a record without a relation (isLocatedAt) results in the warning "Relation (isLocatedAt)-This is a mandatory element for this resource or one of its higher descriptive levels (if part of a collection hierarchy)."

*Child levels created from a parent automatically inherit the relation (isLocatedAt) data.
*If User deletes data from required fields in child level, this results in the warning: "Identifier - This is a mandatory element". "Title - This is a mandatory element." "Relation(isLocatedAt)-This is a mandatory element."

== ISAAR template ==

*The following fields in the edit screen have asterisks next to the field labels: type of entity, authorized form of name, dates of existence and description identifier.
*Saving a record without a type of entity results in the warning "Type of entity - This is a mandatory element."
*Saving a record without an authorized form of name results in the warning "Authorized form of name - This is a mandatory element."
*Saving a record without dates of existence results in the warning "Dates of existence - This is a mandatory element."
*Saving a record without an authority record identifier results in the warning "Description identifier - This is a mandatory element."
*User is prevented from creating a relationship between an ISAAR record and itself.

== ISDIAH template ==

*The following fields in the edit screen have asterisks next to the field labels: identifier, authorized form of name, contact information.
*Saving a record without an identifier results in the warning "Identifier - This is a mandatory element."
*Saving a record without an authorized form of name results in the warning "Authorized form of name - This is a mandatory element."
*Saving a record without at least one of city, country, postal code, region or street address results in the warning "Contact information - You must at least include one of the following location or address fields: city, country, postal code, region or street address."

== ISDF template ==

*The following fields in the edit screen have asterisks next to the field labels: type, authorized form of name, description identifier.
*Saving a record without a type results in the warning "Type - This is a mandatory element."
*Saving a record without an authorized form of name results in the warning "Authorized form of name - This is a mandatory element."
*Saving a record without a function description identifier results in the warning "Description identifier - This is a mandatory element."
*User is prevented from creating a relationship between an ISDF record and itself.

== Term template ==
*Cannot select a broad term that is the same as a the current term
*Cannot select a broad term that is a narrow term of the current term
*Cannot select a related term that is the same as the current term
*Cannot select a related term that is a broad term of the current term
*Cannot select a related term that is a narrow term of the current term

== User edit template ==
*The following fields in the edit screen have asterisks next to the field labels: username, email, password, confirm password
*Saving a record without a username results in the warning "Required" appearing above the field and the record does not save.
*Saving a record without an email results in the warning "Required" appearing above the field and the record does not save.
*Saving a record without a password results in the warning "Required" appearing above the field and the record does not save.
*Saving a record without confirming password results in the warning "Your password confirmation did not match your password" and the record does not save.

== Accession record edit template ==
*The following fields in the edit screen have asterisks next to the field labels: acquisition date, immediate source of acquisition, location information. The record can be saved, even with a warning.
*Saving a record without an acquisition date results in the warning "Acquisition date- This is a mandatory element"
*Saving a record without a source of acquisition results in the warning "Source of acquisition - This is a mandatory element"
*Saving a record without location information results in the warning "Location information - This is a mandatory element"

[[Category:Development documentation]]
__NOTOC__

Development/Functional testing/Validation tests

2020-07-07T23:29:34Z

JennR: /* RAD template */

{{#pagetitle: Validation tests }}
[[Main Page]] > [[Development]] > [[Development/Functional testing|Functional testing]] > Validation tests

== ISAD(G) template ==

*The following fields in the edit screen have asterisks next to the field labels: identifier, title, dates(s), level of description, extent and medium, name of creator(s).
*Saving a record without an identifier results in the warning "Identifier - This is a mandatory element."
*Saving a record without a title results in the warning "Title - This is a mandatory element."
*Saving a record with none of the date fields (start year, end year or date display) results in the warning "Date(s) - This is a mandatory element."
*Saving a record with one of the date fields (start year, end year or date display) results in no warning about dates.
*Saving a record without extent and medium results in the warning "Extent and medium - This is a mandatory element."
*Saving a record without a creator when no creator has been entered at a higher level of description results in the warning "This archival description, or one of its higher levels, requires at least one creator."
*Saving a record without a creator when a creator has been entered at a higher level of description results in no warning about creator.
*Saving a child record with a creation start year that is earlier than the creation start year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with a creation end year that is later than the creation end year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with a creation start year that is the same as the creation start year for the parent record results in no warning.
*Saving a child record with a creation end year that is the same as the creation end year for the parent record results in no warning.
*Saving a child record with an accumulation start year that is earlier than the accumulation start year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with an accumulation end year that is later than the accumulation end year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with an accumulation start year that is earlier than the creation start year for the parent record results in no warning.
*Saving a child record with an accumulation end year that is later than the creation end year for the parent record results in no warning.
*Saving a child record with an accumulation start year that is the same as the accumulation start year for the parent record results in no warning.
*Saving a child record with an accumulation end year that is the same as the accumulation end year for the parent record results in no warning.
*Saving a child record with a level of description that is at a higher or the same level of aggregation as the parent record results in the warning "Level of description - Value (eg "Fonds") is not consistent with higher levels."
*AtoM is designed to be permissive and it won't check every combination of parent-child. But, validation will take place and warnings will be given in most instances when the level of description being saved does not fit in to the expected hierarchical archival structure.
Test as follows:
**A fonds cannot be a child level of a fonds
**A fonds cannot be a child level of a series
**A fonds cannot be a child level of a file
**A fonds cannot be a child level of an item
**A series cannot be a child level of a file
**A series cannot be a child level of an item
**A file cannot be a child level of a file
**A file cannot be a child level of an item
**An item cannot be a child level of an item

== RAD template ==
*The following fields in the edit screen have asterisks next to the field labels: title proper, level of description, physical description and scope and content. The date field is mandatory at the highest descriptive level, but not at lower levels; therefore, no asterisk appears next to the date entry field.
*Saving a record without a date results in the warning "This archival description requires at least one date."

*Saving a record without a title proper results in the warning "Title - This is a mandatory element"
*Saving a record without a level of description results in the warning "Level of description - This is a mandatory element"
*Saving a record without a physical description results in the warning "Physical description - This is a mandatory element"
*Saving a record without a scope and content results in the warning "Scope and content - This is a mandatory element"

*Saving a child record without a title proper results in the warning "Title - This is a mandatory element"
*Saving a child record without a level of description results in the warning "Level of description - This is a mandatory element"
*Saving a child record without a physical description results in the warning "Physical description - This is a mandatory element"
*Saving a child record without a scope and content results in the warning "Scope and content - This is a mandatory element"

*Saving a child record without a date results in the warning "This archival description requires at least one date."
*Saving a child record with a start date prior to the parent start date results in the warning "Date(s) are not consistent with higher levels"
*Saving a child record with an end date later than the parent end date results in the warning "Date(s) are not consistent with higher levels"

*Saving a child record with a level of description that is at a higher or the same level of aggregation as the parent record results in the warning "Level of description - Value (eg "Fonds") is not consistent with higher levels."
*AtoM is designed to be permissive and it won't check every combination of parent-child. But, validation will take place and warnings will be given in most instances when the level of description being saved does not fit in to the expected hierarchical archival structure.
Test as follows:
**A fonds cannot be a child level of a fonds
**A fonds cannot be a child level of a series
**A fonds cannot be a child level of a file
**A fonds cannot be a child level of an item
**A series cannot be a child level of a file
**A series cannot be a child level of an item
**A file cannot be a child level of a file
**A file cannot be a child level of an item
**An item cannot be a child level of an item

== Dublin Core template ==

*The following fields in the edit screen have asterisks next to the field labels: identifier, title, and relation (isLocatedAt).
*Saving a record without an identifier results in the warning "Identifier - This is a mandatory element for this resource or one of its higher descriptive levels (if part of a collection hierarchy)." Issue 2340
*Saving a record without a title results in the warning "Title - This is a mandatory element for this resource or one of its higher descriptive levels (if part of a collection hierarchy)."
*Saving a record without a relation (isLocatedAt) results in the warning "Relation (isLocatedAt)-This is a mandatory element for this resource or one of its higher descriptive levels (if part of a collection hierarchy)."

*Child levels created from a parent automatically inherit the relation (isLocatedAt) data.
*If User deletes data from required fields in child level, this results in the warning: "Identifier - This is a mandatory element". "Title - This is a mandatory element." "Relation(isLocatedAt)-This is a mandatory element."

== ISAAR template ==

*The following fields in the edit screen have asterisks next to the field labels: type of entity, authorized form of name, dates of existence and description identifier.
*Saving a record without a type of entity results in the warning "Type of entity - This is a mandatory element."
*Saving a record without an authorized form of name results in the warning "Authorized form of name - This is a mandatory element."
*Saving a record without dates of existence results in the warning "Dates of existence - This is a mandatory element."
*Saving a record without an authority record identifier results in the warning "Description identifier - This is a mandatory element."
*User is prevented from creating a relationship between an ISAAR record and itself.

== ISDIAH template ==

*The following fields in the edit screen have asterisks next to the field labels: identifier, authorized form of name, contact information.
*Saving a record without an identifier results in the warning "Identifier - This is a mandatory element."
*Saving a record without an authorized form of name results in the warning "Authorized form of name - This is a mandatory element."
*Saving a record without at least one of city, country, postal code, region or street address results in the warning "Contact information - You must at least include one of the following location or address fields: city, country, postal code, region or street address."

== ISDF template ==

*The following fields in the edit screen have asterisks next to the field labels: type, authorized form of name, description identifier.
*Saving a record without a type results in the warning "Type - This is a mandatory element."
*Saving a record without an authorized form of name results in the warning "Authorized form of name - This is a mandatory element."
*Saving a record without a function description identifier results in the warning "Description identifier - This is a mandatory element."
*User is prevented from creating a relationship between an ISDF record and itself.

== Term template ==
*Cannot select a broad term that is the same as a the current term
*Cannot select a broad term that is a narrow term of the current term
*Cannot select a related term that is the same as the current term
*Cannot select a related term that is a broad term of the current term
*Cannot select a related term that is a narrow term of the current term

== User edit template ==
*The following fields in the edit screen have asterisks next to the field labels: username, email, password, confirm password
*Saving a record without a username results in the warning "Required" appearing above the field and the record does not save.
*Saving a record without an email results in the warning "Required" appearing above the field and the record does not save.
*Saving a record without a password results in the warning "Required" appearing above the field and the record does not save.
*Saving a record without confirming password results in the warning "Your password confirmation did not match your password" and the record does not save.

== Accession record edit template ==
*The following fields in the edit screen have asterisks next to the field labels: acquisition date, immediate source of acquisition, location information. The record can be saved, even with a warning.
*Saving a record without an acquisition date results in the warning "Acquisition date- This is a mandatory element"
*Saving a record without a source of acquisition results in the warning "Source of acquisition - This is a mandatory element"
*Saving a record without location information results in the warning "Location information - This is a mandatory element"

[[Category:Development documentation]]
__NOTOC__

Development/Functional testing/Validation tests

2020-07-07T23:04:28Z

JennR: /* ISAD(G) template */

{{#pagetitle: Validation tests }}
[[Main Page]] > [[Development]] > [[Development/Functional testing|Functional testing]] > Validation tests

== ISAD(G) template ==

*The following fields in the edit screen have asterisks next to the field labels: identifier, title, dates(s), level of description, extent and medium, name of creator(s).
*Saving a record without an identifier results in the warning "Identifier - This is a mandatory element."
*Saving a record without a title results in the warning "Title - This is a mandatory element."
*Saving a record with none of the date fields (start year, end year or date display) results in the warning "Date(s) - This is a mandatory element."
*Saving a record with one of the date fields (start year, end year or date display) results in no warning about dates.
*Saving a record without extent and medium results in the warning "Extent and medium - This is a mandatory element."
*Saving a record without a creator when no creator has been entered at a higher level of description results in the warning "This archival description, or one of its higher levels, requires at least one creator."
*Saving a record without a creator when a creator has been entered at a higher level of description results in no warning about creator.
*Saving a child record with a creation start year that is earlier than the creation start year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with a creation end year that is later than the creation end year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with a creation start year that is the same as the creation start year for the parent record results in no warning.
*Saving a child record with a creation end year that is the same as the creation end year for the parent record results in no warning.
*Saving a child record with an accumulation start year that is earlier than the accumulation start year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with an accumulation end year that is later than the accumulation end year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with an accumulation start year that is earlier than the creation start year for the parent record results in no warning.
*Saving a child record with an accumulation end year that is later than the creation end year for the parent record results in no warning.
*Saving a child record with an accumulation start year that is the same as the accumulation start year for the parent record results in no warning.
*Saving a child record with an accumulation end year that is the same as the accumulation end year for the parent record results in no warning.
*Saving a child record with a level of description that is at a higher or the same level of aggregation as the parent record results in the warning "Level of description - Value (eg "Fonds") is not consistent with higher levels."
*AtoM is designed to be permissive and it won't check every combination of parent-child. But, validation will take place and warnings will be given in most instances when the level of description being saved does not fit in to the expected hierarchical archival structure.
Test as follows:
**A fonds cannot be a child level of a fonds
**A fonds cannot be a child level of a series
**A fonds cannot be a child level of a file
**A fonds cannot be a child level of an item
**A series cannot be a child level of a file
**A series cannot be a child level of an item
**A file cannot be a child level of a file
**A file cannot be a child level of an item
**An item cannot be a child level of an item

== RAD template ==
*The following fields in the edit screen have asterisks next to the field labels: title proper, level of description, physical description and scope and content. The date field is mandatory at the highest descriptive level, but not at lower levels; therefore, no asterisk appears next to the date entry field.
*Saving a record without a date results in the warning "This archival description requires at least one date."

*Saving a record without a title proper results in the warning "Title - This is a mandatory element"
*Saving a record without a level of description results in the warning "Level of description - This is a mandatory element"
*Saving a record without a physical description results in the warning "Physical description - This is a mandatory element"
*Saving a record without a scope and content results in the warning "Scope and content - This is a mandatory element"

*Saving a child record without a title proper results in the warning "Title - This is a mandatory element"
*Saving a child record without a level of description results in the warning "Level of description - This is a mandatory element"
*Saving a child record without a physical description results in the warning "Physical description - This is a mandatory element"
*Saving a child record without a scope and content results in the warning "Scope and content - This is a mandatory element"

*Saving a child record without a date results in the warning "This archival description requires at least one date."
*Saving a child record with a start date prior to the parent start date results in the warning "Date(s) are not consistent with higher levels"
*Saving a child record with an end date later than the parent end date results in the warning "Date(s) are not consistent with higher levels"

*Saving a child record with a level of description that is at a higher level of aggregation than the parent record results in the warning "Level of description - Value (eg "Fonds") is not consistent with higher levels." Test as follows:
**A fonds cannot be a child level of a subfonds
**A fonds cannot be a child level of a series
**A fonds cannot be a child level of a subseries
**A fonds cannot be a child level of a file
**A fonds cannot be a child level of an item
**A subfonds cannot be a child level of a collection
**A subfonds cannot be a child level of a series
**A subfonds cannot be a child level of a subseries
**A subfonds cannot be a child level of a file
**A subfonds cannot be a child level of an item
**A collection cannot be a child level of a subfonds
**A collection cannot be a child level of a series
**A collection cannot be a child level of a subseries
**A collection cannot be a child level of a file
**A collection cannot be a child level of an item
**A series cannot be a child level of a subseries
**A series cannot be a child level of a file
**A series cannot be a child level of an item
**A subseries cannot be a child level of a file
**A subseries cannot be a child level of an item
**A file cannot be a child level of an item

*Saving a child record with a level of description that is the same level of aggregation as the parent record results in the warning "Level of description - Value (eg "Fonds") is not consistent with higher levels." Test as follows:
**A fonds cannot be a child level of a fonds
**A fonds cannot be a child level of a collection
**A collection cannot be a child level of a collection
**A collection cannot be a child level of a fonds
**A subfonds cannot be a child level of a subfonds
**A series cannot be a child level of a series
**A subseries cannot be a child level of a subseries
**A file cannot be a child level of a file
**An item cannot be a child level of an item

== Dublin Core template ==

*The following fields in the edit screen have asterisks next to the field labels: identifier, title, and relation (isLocatedAt).
*Saving a record without an identifier results in the warning "Identifier - This is a mandatory element for this resource or one of its higher descriptive levels (if part of a collection hierarchy)." Issue 2340
*Saving a record without a title results in the warning "Title - This is a mandatory element for this resource or one of its higher descriptive levels (if part of a collection hierarchy)."
*Saving a record without a relation (isLocatedAt) results in the warning "Relation (isLocatedAt)-This is a mandatory element for this resource or one of its higher descriptive levels (if part of a collection hierarchy)."

*Child levels created from a parent automatically inherit the relation (isLocatedAt) data.
*If User deletes data from required fields in child level, this results in the warning: "Identifier - This is a mandatory element". "Title - This is a mandatory element." "Relation(isLocatedAt)-This is a mandatory element."

== ISAAR template ==

*The following fields in the edit screen have asterisks next to the field labels: type of entity, authorized form of name, dates of existence and description identifier.
*Saving a record without a type of entity results in the warning "Type of entity - This is a mandatory element."
*Saving a record without an authorized form of name results in the warning "Authorized form of name - This is a mandatory element."
*Saving a record without dates of existence results in the warning "Dates of existence - This is a mandatory element."
*Saving a record without an authority record identifier results in the warning "Description identifier - This is a mandatory element."
*User is prevented from creating a relationship between an ISAAR record and itself.

== ISDIAH template ==

*The following fields in the edit screen have asterisks next to the field labels: identifier, authorized form of name, contact information.
*Saving a record without an identifier results in the warning "Identifier - This is a mandatory element."
*Saving a record without an authorized form of name results in the warning "Authorized form of name - This is a mandatory element."
*Saving a record without at least one of city, country, postal code, region or street address results in the warning "Contact information - You must at least include one of the following location or address fields: city, country, postal code, region or street address."

== ISDF template ==

*The following fields in the edit screen have asterisks next to the field labels: type, authorized form of name, description identifier.
*Saving a record without a type results in the warning "Type - This is a mandatory element."
*Saving a record without an authorized form of name results in the warning "Authorized form of name - This is a mandatory element."
*Saving a record without a function description identifier results in the warning "Description identifier - This is a mandatory element."
*User is prevented from creating a relationship between an ISDF record and itself.

== Term template ==
*Cannot select a broad term that is the same as a the current term
*Cannot select a broad term that is a narrow term of the current term
*Cannot select a related term that is the same as the current term
*Cannot select a related term that is a broad term of the current term
*Cannot select a related term that is a narrow term of the current term

== User edit template ==
*The following fields in the edit screen have asterisks next to the field labels: username, email, password, confirm password
*Saving a record without a username results in the warning "Required" appearing above the field and the record does not save.
*Saving a record without an email results in the warning "Required" appearing above the field and the record does not save.
*Saving a record without a password results in the warning "Required" appearing above the field and the record does not save.
*Saving a record without confirming password results in the warning "Your password confirmation did not match your password" and the record does not save.

== Accession record edit template ==
*The following fields in the edit screen have asterisks next to the field labels: acquisition date, immediate source of acquisition, location information. The record can be saved, even with a warning.
*Saving a record without an acquisition date results in the warning "Acquisition date- This is a mandatory element"
*Saving a record without a source of acquisition results in the warning "Source of acquisition - This is a mandatory element"
*Saving a record without location information results in the warning "Location information - This is a mandatory element"

[[Category:Development documentation]]
__NOTOC__

Development/Functional testing/Validation tests

2020-07-07T23:03:40Z

JennR: /* ISAD(G) template */

{{#pagetitle: Validation tests }}
[[Main Page]] > [[Development]] > [[Development/Functional testing|Functional testing]] > Validation tests

== ISAD(G) template ==

*The following fields in the edit screen have asterisks next to the field labels: identifier, title, dates(s), level of description, extent and medium, name of creator(s).
*Saving a record without an identifier results in the warning "Identifier - This is a mandatory element."
*Saving a record without a title results in the warning "Title - This is a mandatory element."
*Saving a record with none of the date fields (start year, end year or date display) results in the warning "Date(s) - This is a mandatory element."
*Saving a record with one of the date fields (start year, end year or date display) results in no warning about dates.
*Saving a record without extent and medium results in the warning "Extent and medium - This is a mandatory element."
*Saving a record without a creator when no creator has been entered at a higher level of description results in the warning "This archival description, or one of its higher levels, requires at least one creator."
*Saving a record without a creator when a creator has been entered at a higher level of description results in no warning about creator.
*Saving a child record with a creation start year that is earlier than the creation start year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with a creation end year that is later than the creation end year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with a creation start year that is the same as the creation start year for the parent record results in no warning.
*Saving a child record with a creation end year that is the same as the creation end year for the parent record results in no warning.
*Saving a child record with an accumulation start year that is earlier than the accumulation start year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with an accumulation end year that is later than the accumulation end year for the parent record results in the warning "Date(s) - are not consistent with higher levels."
*Saving a child record with an accumulation start year that is earlier than the creation start year for the parent record results in no warning.
*Saving a child record with an accumulation end year that is later than the creation end year for the parent record results in no warning.
*Saving a child record with an accumulation start year that is the same as the accumulation start year for the parent record results in no warning.
*Saving a child record with an accumulation end year that is the same as the accumulation end year for the parent record results in no warning.
*Saving a child record with a level of description that is at a higher or the same level of aggregation as the parent record results in the warning "Level of description - Value (eg "Fonds") is not consistent with higher levels."
*AtoM is designed to be permissive and it won't check every combination of parent-child. But, validation will take place and warnings will be given in most instances when the level of description being saved does not fit in to the expected hierarchical archival structure.
Test as follows:
**A fonds cannot be a child level of a fonds
**A fonds cannot be a child level of a series
**A fonds cannot be a child level of a file
**A fonds cannot be a child level of an item
**A series cannot be a child level of a file
**A series cannot be a child level of an item
**A file cannot be a child level of a file
**A file cannot be a child level of an item
**An item cannot be a child level of an item

== RAD template ==
*The following fields in the edit screen have asterisks next to the field labels: title proper, level of description, physical description and scope and content. The date field is mandatory at the highest descriptive level, but not at lower levels; therefore, no asterisk appears next to the date entry field.
*Saving a record without a date results in the warning "This archival description requires at least one date."

*Saving a record without a title proper results in the warning "Title - This is a mandatory element"
*Saving a record without a level of description results in the warning "Level of description - This is a mandatory element"
*Saving a record without a physical description results in the warning "Physical description - This is a mandatory element"
*Saving a record without a scope and content results in the warning "Scope and content - This is a mandatory element"

*Saving a child record without a title proper results in the warning "Title - This is a mandatory element"
*Saving a child record without a level of description results in the warning "Level of description - This is a mandatory element"
*Saving a child record without a physical description results in the warning "Physical description - This is a mandatory element"
*Saving a child record without a scope and content results in the warning "Scope and content - This is a mandatory element"

*Saving a child record without a date results in the warning "This archival description requires at least one date."
*Saving a child record with a start date prior to the parent start date results in the warning "Date(s) are not consistent with higher levels"
*Saving a child record with an end date later than the parent end date results in the warning "Date(s) are not consistent with higher levels"

*Saving a child record with a level of description that is at a higher level of aggregation than the parent record results in the warning "Level of description - Value (eg "Fonds") is not consistent with higher levels." Test as follows:
**A fonds cannot be a child level of a subfonds
**A fonds cannot be a child level of a series
**A fonds cannot be a child level of a subseries
**A fonds cannot be a child level of a file
**A fonds cannot be a child level of an item
**A subfonds cannot be a child level of a collection
**A subfonds cannot be a child level of a series
**A subfonds cannot be a child level of a subseries
**A subfonds cannot be a child level of a file
**A subfonds cannot be a child level of an item
**A collection cannot be a child level of a subfonds
**A collection cannot be a child level of a series
**A collection cannot be a child level of a subseries
**A collection cannot be a child level of a file
**A collection cannot be a child level of an item
**A series cannot be a child level of a subseries
**A series cannot be a child level of a file
**A series cannot be a child level of an item
**A subseries cannot be a child level of a file
**A subseries cannot be a child level of an item
**A file cannot be a child level of an item

*Saving a child record with a level of description that is the same level of aggregation as the parent record results in the warning "Level of description - Value (eg "Fonds") is not consistent with higher levels." Test as follows:
**A fonds cannot be a child level of a fonds
**A fonds cannot be a child level of a collection
**A collection cannot be a child level of a collection
**A collection cannot be a child level of a fonds
**A subfonds cannot be a child level of a subfonds
**A series cannot be a child level of a series
**A subseries cannot be a child level of a subseries
**A file cannot be a child level of a file
**An item cannot be a child level of an item

== Dublin Core template ==

*The following fields in the edit screen have asterisks next to the field labels: identifier, title, and relation (isLocatedAt).
*Saving a record without an identifier results in the warning "Identifier - This is a mandatory element for this resource or one of its higher descriptive levels (if part of a collection hierarchy)." Issue 2340
*Saving a record without a title results in the warning "Title - This is a mandatory element for this resource or one of its higher descriptive levels (if part of a collection hierarchy)."
*Saving a record without a relation (isLocatedAt) results in the warning "Relation (isLocatedAt)-This is a mandatory element for this resource or one of its higher descriptive levels (if part of a collection hierarchy)."

*Child levels created from a parent automatically inherit the relation (isLocatedAt) data.
*If User deletes data from required fields in child level, this results in the warning: "Identifier - This is a mandatory element". "Title - This is a mandatory element." "Relation(isLocatedAt)-This is a mandatory element."

== ISAAR template ==

*The following fields in the edit screen have asterisks next to the field labels: type of entity, authorized form of name, dates of existence and description identifier.
*Saving a record without a type of entity results in the warning "Type of entity - This is a mandatory element."
*Saving a record without an authorized form of name results in the warning "Authorized form of name - This is a mandatory element."
*Saving a record without dates of existence results in the warning "Dates of existence - This is a mandatory element."
*Saving a record without an authority record identifier results in the warning "Description identifier - This is a mandatory element."
*User is prevented from creating a relationship between an ISAAR record and itself.

== ISDIAH template ==

*The following fields in the edit screen have asterisks next to the field labels: identifier, authorized form of name, contact information.
*Saving a record without an identifier results in the warning "Identifier - This is a mandatory element."
*Saving a record without an authorized form of name results in the warning "Authorized form of name - This is a mandatory element."
*Saving a record without at least one of city, country, postal code, region or street address results in the warning "Contact information - You must at least include one of the following location or address fields: city, country, postal code, region or street address."

== ISDF template ==

*The following fields in the edit screen have asterisks next to the field labels: type, authorized form of name, description identifier.
*Saving a record without a type results in the warning "Type - This is a mandatory element."
*Saving a record without an authorized form of name results in the warning "Authorized form of name - This is a mandatory element."
*Saving a record without a function description identifier results in the warning "Description identifier - This is a mandatory element."
*User is prevented from creating a relationship between an ISDF record and itself.

== Term template ==
*Cannot select a broad term that is the same as a the current term
*Cannot select a broad term that is a narrow term of the current term
*Cannot select a related term that is the same as the current term
*Cannot select a related term that is a broad term of the current term
*Cannot select a related term that is a narrow term of the current term

== User edit template ==
*The following fields in the edit screen have asterisks next to the field labels: username, email, password, confirm password
*Saving a record without a username results in the warning "Required" appearing above the field and the record does not save.
*Saving a record without an email results in the warning "Required" appearing above the field and the record does not save.
*Saving a record without a password results in the warning "Required" appearing above the field and the record does not save.
*Saving a record without confirming password results in the warning "Your password confirmation did not match your password" and the record does not save.

== Accession record edit template ==
*The following fields in the edit screen have asterisks next to the field labels: acquisition date, immediate source of acquisition, location information. The record can be saved, even with a warning.
*Saving a record without an acquisition date results in the warning "Acquisition date- This is a mandatory element"
*Saving a record without a source of acquisition results in the warning "Source of acquisition - This is a mandatory element"
*Saving a record without location information results in the warning "Location information - This is a mandatory element"

[[Category:Development documentation]]
__NOTOC__