We launched the new OAC system with a snapshot of all published finding aids as of June 30, 2025. As part of this process, we ran a bulk validation process on existing finding aids to check the EAD encoding, and also identify any issues with finding aids that would result in display errors in the new OAC website. We identified 1,079 EAD finding aids (approximately 2% of all migrated EAD finding aids total) that initially resulted in display errors in the new OAC website.
Our EAD migration errors summary provided additional details about these finding aids and error reports, at the time that we cutover to the new OAC system on July 23, 2025. It also summarized our proposed strategy to address these EAD validation errors.
Post-launch and through September, we implemented adjustments to ArcLight’s indexing and display settings, and completed the migration of all remaining EAD finding aids. These adjustments addressed the following key encoding issues that previously blocked migration of the finding aids:
Failed to parse title: the finding aid does not contain a <unittitle> in ead/archdesc, indicating the title of the collection (for use within search/browse results and finding aid displays). We adjusted ArcLight to use the <titleproper> as a fallback.
Failed to parse collection number: the finding aid does not contain a <unitid> in ead/archdesc, indicating the collection number/identifier for the collection (for use within finding aid displays). We adjusted ArcLight to use the EAD filename as a fallback.
Components cannot have level=collection: the finding aid includes Component elements, with the LEVEL attribute set to "collection"; these previously failed to render in the display. We subsequently modified ArcLight to ignore this particular LEVEL attribute at the Component level.
No title for empty component: the finding aid includes Component <c0#> elements with no additional descriptive information, such as a title, date, file/item number, or container. These specific components will not display (but will not prevent the display of the overall finding aid).
As of October 2025, we are still working on completing the migration of some supplemental PDF files (denoted as Failed to import supplemental files in the error reports) and/or resolving URL links to them.
Curious about our progress? Take a look at our work-in-progress overview page to check the status.
Status
Resolved
Issue
We launched the new OAC system with a snapshot of all published finding aids as of June 30, 2025. As part of this process, we ran a bulk validation process on existing finding aids to check the EAD encoding, and also identify any issues with finding aids that would result in display errors in the new OAC website. We identified 1,079 EAD finding aids (approximately 2% of all migrated EAD finding aids total) that initially resulted in display errors in the new OAC website.
Our EAD migration errors summary provided additional details about these finding aids and error reports, at the time that we cutover to the new OAC system on July 23, 2025. It also summarized our proposed strategy to address these EAD validation errors.
Post-launch and through September, we implemented adjustments to ArcLight’s indexing and display settings, and completed the migration of all remaining EAD finding aids. These adjustments addressed the following key encoding issues that previously blocked migration of the finding aids:
Failed to parse title: the finding aid does not contain a <unittitle> in ead/archdesc, indicating the title of the collection (for use within search/browse results and finding aid displays). We adjusted ArcLight to use the <titleproper> as a fallback.
Failed to parse collection number: the finding aid does not contain a <unitid> in ead/archdesc, indicating the collection number/identifier for the collection (for use within finding aid displays). We adjusted ArcLight to use the EAD filename as a fallback.
Components cannot have level=collection: the finding aid includes Component elements, with the LEVEL attribute set to "collection"; these previously failed to render in the display. We subsequently modified ArcLight to ignore this particular LEVEL attribute at the Component level.
No title for empty component: the finding aid includes Component <c0#> elements with no additional descriptive information, such as a title, date, file/item number, or container. These specific components will not display (but will not prevent the display of the overall finding aid).
As of October 2025, we are still working on completing the migration of some supplemental PDF files (denoted as Failed to import supplemental files in the error reports) and/or resolving URL links to them.
Curious about our progress? Take a look at our work-in-progress overview page to check the status.
0 Votes
0 Comments
Login or Sign up to post a comment