From jlandis at auctr.edu  Fri Dec  1 09:48:58 2023
From: jlandis at auctr.edu (Cliff Landis)
Date: Fri, 1 Dec 2023 14:48:58 +0000
Subject: [Archivesspace_Users_Group] Help
	changing	the	<repositoryIdentifier> value in the OAI-PMH feed?
In-Reply-To: <SN6PR01MB47493195D8D119BF489FECB7DF82A@SN6PR01MB4749.prod.exchangelabs.com>
References: <538C739047C356499F2F0D78696DA4FE10FE02FD@RWWLEXCHSRV01.RWWL-MAIN.AUCTR.EDU>
 <SN6PR01MB47493195D8D119BF489FECB7DF82A@SN6PR01MB4749.prod.exchangelabs.com>
Message-ID: <538C739047C356499F2F0D78696DA4FE10FE5F2A@RWWLEXCHSRV01.RWWL-MAIN.AUCTR.EDU>

Hi Saron,

That did the trick!  Thanks for taking the time to walk me through it ? very much appreciated!

All the best,

Cliff Landis  (he/him/his<https://www.glsen.org/activity/pronouns-guide-glsen>)
Digital Initiatives Librarian
Atlanta University Center Robert W. Woodruff Library
111 James P. Brawley Drive, SW
Atlanta, GA  30314
404-978-2155 (v)
http://www.auctr.edu<http://www.auctr.edu/>
jlandis at auctr.edu<mailto:jlandis at auctr.edu>

We will always provide service that exceeds the customer?s expectation? Because we care!

From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Tran, Saron Tech
Sent: Thursday, November 30, 2023 11:57 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Help changing the <repositoryIdentifier> value in the OAI-PMH feed?

Hi Cliff.

The <repositoryIdentifier> element is from the staff interface ?OAI-PMH Settings? page.  It uses the OAI Record Prefix where it removes the ?oai:? part if you still have it there otherwise it will just take the value entered there (I think this is it as I backtracked from just trying it in our test instance-- https://github.com/archivesspace/archivesspace/blob/a81ea29ea0167374ef7d38e8a5631627b9cd1d2d/backend/app/lib/oai/oai_gem_patches/identify_response.rb#L22 ).  It did require me to restart the application when I changed the OAI Record Prefix field to take place in the https://archives.lib.ku.edu/oai?verb=Identify where I found the <repositoryIdentifier> element.

It looks like the default value in that field is:  oai:archivesspace which is why I think you see ArchivesSpace in the <repositoryIdentifier> element



From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Cliff Landis <jlandis at auctr.edu<mailto:jlandis at auctr.edu>>
Date: Thursday, November 30, 2023 at 10:09?AM
To: archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org> <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Help changing the <repositoryIdentifier> value in the OAI-PMH feed?
Hi folks,

We?re trying to set up the ArchivesSpace OAI-PMH feed in Digital Collections Gateway (DCG) so that our finding aids can appear in WorldCat.

Unfortunately, the OAI-PMH feed that is coming out of ArchivesSpace isn?t passing the pre-check validator in DCG.

We reached out to OCLC, and they said to test the feed using the validator at https://www.openarchives.org/Register/ValidateSite.

When we did so, we got a failure for the <repositoryIdentifier> element, because the value is currently set to ?archivesspace? rather than to our domain ?auctr.edu?.  The domain is what?s required in that element according to the guidelines<https://www.openarchives.org/OAI/2.0/guidelines-oai-identifier.htm>.

There?s no option to change that particular element, either in the back-end config.rb file<https://archivesspace.github.io/tech-docs/customization/configuration.html>, or in the staff interface ?OAI-PMH Settings? page.

Is there any other way to change this value?  Is there something that I?m missing?

Thanks in advance!

Cliff Landis  (he/him/his<https://www.glsen.org/activity/pronouns-guide-glsen>)
Digital Initiatives Librarian
Atlanta University Center Robert W. Woodruff Library
111 James P. Brawley Drive, SW
Atlanta, GA  30314
404-978-2155 (v)
http://www.auctr.edu<http://www.auctr.edu/>
jlandis at auctr.edu<mailto:jlandis at auctr.edu>

We will always provide service that exceeds the customer?s expectation? Because we care!

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231201/2e959dea/attachment.html>

From rtwilson at cornell.edu  Fri Dec  1 10:20:23 2023
From: rtwilson at cornell.edu (Robert T. Wilson)
Date: Fri, 1 Dec 2023 15:20:23 +0000
Subject: [Archivesspace_Users_Group] update-feed api endpoint behavior
Message-ID: <BN7PR04MB525044698665A315B05D58F2D381A@BN7PR04MB5250.namprd04.prod.outlook.com>

Hi all,

We have an integration with our ILS that currently uses the update-feed endpoint:https://archivesspace.github.io/archivesspace/api/#get-a-stream-of-updated-records whenever a resource or top container is updated.

Does anyone know precise behavior that triggers that feed? I ask because working on a migration and db updates and batch api updates are not triggering the update-feed. Wondering what I might need to do to get these records in update feed stream for our integration to do its thing. Or if I'm just missing something.

Thanks for any insight,

Robert

Robert T. Wilson (he/him)
Cloud Systems Administrator
Cornell University Library
rtwilson at cornell.edu
607.254.3483
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231201/0b564fd8/attachment.html>

From bailey-grace.harrell at lyrasis.org  Fri Dec  1 11:07:03 2023
From: bailey-grace.harrell at lyrasis.org (Bailey-Grace Harrell)
Date: Fri, 1 Dec 2023 16:07:03 +0000
Subject: [Archivesspace_Users_Group] ArchivesSpace Update - November 2023
Message-ID: <CYYPR22MB415865820ACD31F73D4E135AC681A@CYYPR22MB4158.namprd22.prod.outlook.com>

  [cid:image001.jpg at 01DA2444.5D7C3C50]


ArchivesSpace Update ? November 2023


Upcoming Schedule at a Glance:


December 1: Survey responses due for the ArchivesSpace training topics survey <https://www.surveymonkey.com/r/HXQMDP6>

December 6: Live Demonstration: Overview of the ArchivesSpace Application and Membership Benefits<https://archivesspace.org/archives/8237>

December 8: Last day to volunteer to join the 2024 Virtual Member Forum planning team

December 8: Survey responses due for the ArchivesSpace Multilingual Description survey<https://forms.gle/61QaYtBLr5XywGoc6>



Development


We continue to gather up development and testing work for the next release. As the end of the calendar year is fast approaching, it looks like we will not have time to complete everything that needs to be done to put out another release in 2023. You can expect a new release early in 2024 instead. New development is always up on our test server at https://test.archivesspace.org/staff/.


Transition for ArchivesSpace Listservs


Lyrasis, the organizational home for ArchivesSpace, is planning to transition away from the Mailman platform for listservs to Google Groups in the near future. The ArchivesSpace member listservs, including the Users Group, will become Google Groups with email delivery after the transition. Right now the move is planned to occur between December 26 and January 1. All accounts subscribed to our member listservs at the time of the transition will be moved to the new platform, with equivalent settings to what users have currently.


For now the archives of our listservs will be maintained on the current platform, and will stay there for at least a year. Some details of the transition are still to be determined, including how listserv archives will be available after the planned one year period when they will remain on the current platform. We know that the archives of the Users Group listserv, in particular, are an important source of information for the community and are working to ensure that access to them remains consistent.


If you have any questions about this change, please feel free to get in touch with us at ArchivesSpaceHome at lyrasis.org<mailto:ArchivesSpaceHome at lyrasis.org>.


Survey Participation Requested: Selecting the 2024 ArchivesSpace Community-wide Training Topics


Thank you to everyone who attended an ArchivesSpace community-wide training this year.  The Trainers Corps is currently developing the 2024 training schedule and is requesting community input to help determine future training topics.  A survey for this purpose is available at https://www.surveymonkey.com/r/HXQMDP6. Survey responses are due by December 1, 2023.


Responses to this survey will be used by the Trainers Corps to prioritize offering the top 3 selections over the course of the next year. Please note that in addition to the topics listed on the survey, the Trainers Corps is committed to offering a Basics training in 2024.


ArchivesSpace community-wide training sessions will be 2-3 hours in length, depending on the topic.  These trainings are offered for a fee but ArchivesSpace members receive a substantial discount.


To learn more about ArchivesSpace community-wide training, visit https://archivesspace.org/using-archivesspace/trainings.



ArchivesSpace Virtual Member Forum 2024 - Save the Date and Call for Planning Team Members

Mark your calendars for our 2024 Virtual Member Forum! Taking place March 26-27, 2024, our Virtual Member Forum will be a two-day event spanning a variety of time zones and ArchivesSpace experience levels.

If you are interested in serving on the planning team for this forum, please email Jessica Crouch at jessica.crouch at lyrasis.org<mailto:jessica.crouch at lyrasis.org> by December 8, 2023.  The Virtual Member Forum is one of our largest events of the year and we are looking for volunteers to review proposals, develop the schedule, and help make this forum great!

More information will be provided soon about how to propose a topic or presentation.  Registration will open closer to the event date.  For now, be sure to save the date on your calendar.  We look forward to ?seeing? many of you there.



Live Demonstration: Overview of the ArchivesSpace Application and Membership Benefits

ArchivesSpace is offering a 60-minute demonstration of the ArchivesSpace application open to anyone interested in ArchivesSpace. This demonstration will be offered on December 6, 2023, at 11:00am ET / 8:00am PT.



Date: December 6, 2023

Time: 11:00am ? 12:00pm ET (8:00am ? 9:00am PT)

Where: Zoom

Registration: https://lyrasis.zoom.us/webinar/register/WN_-Who6uezSOGkrGmfGQqEhg



This demo will feature an overview of the application, a brief explanation of the ArchivesSpace Staff and Public User Interfaces and an introduction to the ArchivesSpace member community<https://archivesspace.org/community/whos-using-archivesspace> and member benefits<https://archivesspace.org/community/member-benefits>.  A brief Q&A will follow the demo.  These demos are intended to assist those who are considering using the ArchivesSpace application at their organization to determine if ArchivesSpace is the right tool for their needs.



These demonstrations are not intended for those already using ArchivesSpace or those looking for ArchivesSpace training opportunities<https://archivesspace.org/using-archivesspace/trainings>. The December 6 demo will be recorded and made available with the other freely available resources on our Getting Started webpage<https://archivesspace.org/using-archivesspace/getting-started>.



For more information about this demo, ArchivesSpace, and ArchivesSpace membership, email ArchivesSpaceHome at lyrasis.org<mailto:ArchivesSpaceHome at lyrasis.org>.



ArchivesSpace Multilingual Description Survey

[Posted on behalf of the Usability sub-team of the User Advisory Council]



The ArchivesSpace Usability Subteam is seeking community input on the potential addition of multilingual description support in the application, allowing users to have descriptive information about their holdings in multiple languages within the same record. The survey seeks to assess how ArchivesSpace is currently used and how the addition of this functionality would impact current workflows. Survey responses are due December 8.



Your participation in the survey is voluntary. The survey should take about 5-10 minutes to complete. Please click on the link below to go to the Google Forms survey, or copy and paste the link into your browser:



https://forms.gle/61QaYtBLr5XywGoc6



No personally identifiable information from your responses will be associated with any reports of these data. After completing the survey, we also provide a link to a secondary form for community members to indicate if they would be interested in helping develop a draft specification. Responses to this secondary form are not linked to the initial survey.



Thank you for your time and consideration. If you have any questions, please contact the ArchivesSpace program team at ArchivesSpaceHome at lyrasis.org<mailto:ArchivesSpaceHome at lyrasis.org>.



Christine Di Bella's New Title


We are very pleased to announce that Christine Di Bella?s new title is Senior Program Manager effective November 15.



In her nine years with ArchivesSpace and under Christine?s stewardship, the ArchivesSpace application has become an essential tool for thousands of collecting institutions around the world and the ArchivesSpace program has grown to nearly 500 active member institutions. In close collaboration with the other members of the program team and the community, she has overseen the expansion of the functionality of the application to address all of the major archival functions and the community engagement programming has grown significantly more responsive to users. The program has reached out to new audiences and created impactful partnership programs, such as the ArchivesSpace Diversity Partnership and the Consortium Provider affiliation, and strengthened its Educational Membership Program to better support educators and those entering the profession. Christine?s thoughtful management and care in negotiating the needs of its many stakeholders and keeping forward momentum through challenging times has made ArchivesSpace an exemplar and object of admiration in the wider cultural heritage open-source community.



Going forward, Christine will take an expanded role in working directly with the ArchivesSpace Governance Board and overseeing the technical team, including the Technical Lead. This senior level designation recognizes both the complexity and scale of the program she manages and her depth of expertise in doing so.


Recording available: ArchivesSpace at 10: Reflections on Developing a Sustainable Open-Source Content Management System



Christine Di Bella and Jessica Crouch recently recorded a session for the Coalition of Networked Information?s Project Briefing Series titled ArchivesSpace at 10: Reflections on Developing a Sustainable Open-Source Content Management System.  The recording of that briefing is now available on CNI?s website at https://www.cni.org/topics/special-collections/archivesspace-at-10.


Membership Update

We are excited to welcome our newest members to our community! Some of our new members since November 30th include:

  *   Georgetown Visitation Monastery | Washington, D.C.
  *   Georgetown Visitation Preparatory School | Washington, D.C.
  *   Planting Fields Foundation | Oyster Bay, NY
  *   Visitation Academy of St. Louis | St. Louis, MO
  *   Visitation Monastery | Mendota Heights, MN

As of November 30th, we have 476 General members, 19 Educational Program members, 3 Registered Service Providers, and 1 Consortium Provider.

Thank you to our current ArchivesSpace members<https://archivesspace.org/community/whos-using-archivesspace> for your contribution to the development and sustainability of the ArchivesSpace application.  ArchivesSpace has a membership model<https://archivesspace.org/community/why-become-a-member> to support the continued development of the application and user community and ArchivesSpace members are eligible for a variety of benefits<https://archivesspace.org/community/member-benefits>.  If you are interested in ArchivesSpace membership<https://archivesspace.org/community/making_a_case_for_membership> for your organization, email us at ArchivesSpaceHome at lyrasis.org<mailto:ArchivesSpaceHome at lyrasis.org>.

________________________________

ArchivesSpace monthly updates provide news about ArchivesSpace community and program activities and are sent to our member listservs, the ArchivesSpace Google Group, and SAA?s Collection Management Section listserv, as well as being posted on the ArchivesSpace website. Please feel free to share this update with people you know who have an interest in ArchivesSpace but may not be on one of these lists.



Bailey-Grace Harrell
ArchivesSpace Program Assistant
Bailey-grace.harrell at lyrasis.com<mailto:Bailey-grace.harrell at lyrasis.com>

[signature_3512913459]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231201/8a26c72e/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 68987 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231201/8a26c72e/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 224996 bytes
Desc: image002.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231201/8a26c72e/attachment-0001.png>

From bailey-grace.harrell at lyrasis.org  Tue Dec  5 10:10:08 2023
From: bailey-grace.harrell at lyrasis.org (Bailey-Grace Harrell)
Date: Tue, 5 Dec 2023 15:10:08 +0000
Subject: [Archivesspace_Users_Group] Reminder: Overview of the ArchivesSpace
 Application and Membership Benefits
Message-ID: <CYYPR22MB4158B72E2565543EAAD51778C685A@CYYPR22MB4158.namprd22.prod.outlook.com>

Good morning,

This message is a reminder about the following ArchivesSpace Demo on December 6th.



Live Demonstration: Overview of the ArchivesSpace Application and Membership Benefits

ArchivesSpace is offering a 60-minute demonstration of the ArchivesSpace application open to anyone interested in ArchivesSpace. This demonstration will be offered on December 6, 2023, at 11:00am ET / 8:00am PT.

Date: December 6, 2023
Time: 11:00am ? 12:00pm ET (8:00am ? 9:00am PT)
Where: Zoom
Registration: https://lyrasis.zoom.us/webinar/register/WN_-Who6uezSOGkrGmfGQqEhg

This demo will feature an overview of the application, a brief explanation of the ArchivesSpace Staff and Public User Interfaces and an introduction to the ArchivesSpace member community<https://archivesspace.org/community/whos-using-archivesspace>and member benefits<https://archivesspace.org/community/member-benefits>.  A brief Q&A will follow the demo.  These demos are intended to assist those who are considering using the ArchivesSpace application at their organization to determine if ArchivesSpace is the right tool for their needs.

These demonstrations are not intended for those already using ArchivesSpace or those looking for ArchivesSpace training opportunities<https://archivesspace.org/using-archivesspace/trainings>. The December 6 demo will be recorded and made available with the other freely available resources on our Getting Started webpage<https://archivesspace.org/using-archivesspace/getting-started>.

For more information about this demo, ArchivesSpace, and ArchivesSpace membership, email ArchivesSpaceHome at lyrasis.org<mailto:ArchivesSpaceHome at lyrasis.org>.



Bailey-Grace Harrell
ArchivesSpace Program Assistant
Bailey-grace.harrell at lyrasis.com<mailto:Bailey-grace.harrell at lyrasis.com>

[signature_4225953963]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231205/5e6339a9/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 224996 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231205/5e6339a9/attachment.png>

From morganem at live.unc.edu  Tue Dec  5 10:42:20 2023
From: morganem at live.unc.edu (McKeehan, Morgan)
Date: Tue, 5 Dec 2023 15:42:20 +0000
Subject: [Archivesspace_Users_Group] =?windows-1252?q?Digital_Objects_=96_?=
 =?windows-1252?q?examples_of_ASpace_records_+_repository_objects=3F?=
Message-ID: <BN9PR03MB59794A86E5FCB36879F0C5FDF085A@BN9PR03MB5979.namprd03.prod.outlook.com>

Hi everyone,

I?m looking for examples of how other institutions have handled relationships between ASpace records and digital repository content, in cases when the physical arrangement vs. intellectual arrangement poses object-modeling challenges for digitized representations.

For example, in your systems do you have scenarios when an ASpace archival object record may have many ASpace digital object (DO) records linked to it, with each DO record corresponding to an individual object in your digital repository system? Conversely, perhaps there are also  situations where a single digital repository object contains files/digitized pages that are described by separate archival object records ? ie, a folder of stuff that was digitized as one grouping, but actually corresponds to more than one individual descriptive component?

At my institution, we?re working through these issues as we?re migrating our digitized materials to a new digital repository system at the same time as we?re also migrating our finding aids/archival data to ASpace. We would welcome any examples that others can share, in case you may have approaches from what has worked well, or lessons learned about what to avoid.

Please also feel free to message me off-list if more context or clarification about what I?m asking would be helpful. I?m happy to discuss more about our workflows and object modeling plans so far.

I?d also be happy to set up a zoom call if anyone has examples to share that it would be easier to walk through via zoom. I totally understand there may be examples that just seem too complicated to try to explain in an email!

Here's a little more explanation about the kinds of linking situations I?m asking about:

In our new digital repository, we plan to model digitized materials as repository objects based on the physical containers. For example, all digitized pages from a folder of correspondence would equal 1 repository object (a ?Work?). The URL of the repository object will provide the File Version value for an ASpace Digital Object record, and that DO record will be linked to the relevant archival object record that contains the description for the original materials.

In cases such as a grouping of documents that is housed in a range of physical folders, this will mean many DO records linked to an archival object record. A common scenario is something like: a descriptive component with Title: ?Correspondence, 1800?, housed in ?Folders 65-75?. This arrangement will give us 11 DO records linked to the ?Correspondence, 1800? archival object record. In many cases, folder ranges will be even larger, so there could easily be 20-30 or more DO records linked to an AO record. However, if we instead modeled all scans from Folders 65-75 as 1 object in our digital repository, since each folder contains 100+ pages, that arrangement would be a large and cumbersome repository object for users to navigate. Neither option seems great. We?re interested in learning about how others handle these types of situations!

Thanks for any examples or insights you can share,

Morgan

------------------------
Morgan McKeehan (she/her/hers)
Digital Collections Specialist
University Libraries
The University of North Carolina at Chapel Hill
morganem at email.unc.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231205/b29e2c14/attachment.html>

From lneely at okeeffemuseum.org  Tue Dec  5 12:37:34 2023
From: lneely at okeeffemuseum.org (Liz Neely)
Date: Tue, 5 Dec 2023 17:37:34 +0000
Subject: [Archivesspace_Users_Group] Determining which AO notes are
	published to the PUI (?)
Message-ID: <BY5PR11MB3926FBF6B26CA3482B51F667CE85A@BY5PR11MB3926.namprd11.prod.outlook.com>

Hello,

We are experimenting with using a Related Materials note to include the link to a record in another system that gives access to the related digital materials. I published both the note and subnote, but they are not showing up on the archival object record in the PUI.

I?m testing this with ArchivesSpace 3.4.1.

This is a note type ?Related Materials? with a label of View Digital Materials. In the subnote I include the HTML for the link. Both are published.

[cid:image001.png at 01DA2766.9079F4B0]

But in the PUI, I only see the Ownership and Rights and Explanation of Rights notes. Is there a way that I can have all published notes show on this record? I looked in the config.db but didn?t see anything at this level of specificity.

[A screenshot of a computer  Description automatically generated]

Any advice would be greatly appreciated!

Thank you,
Liz


Liz Neely (she/her)
Curator of Digital Experience
Georgia O?Keeffe Museum
Santa Fe, New Mexico
lneely at gokm.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231205/6fb7e50c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 408598 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231205/6fb7e50c/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 55178 bytes
Desc: image002.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231205/6fb7e50c/attachment-0003.png>

From Courtney.Rookard at nationalww2museum.org  Tue Dec  5 13:01:23 2023
From: Courtney.Rookard at nationalww2museum.org (Courtney Rookard)
Date: Tue, 5 Dec 2023 18:01:23 +0000
Subject: [Archivesspace_Users_Group] Determining which AO notes
	are	published to the PUI (?)
In-Reply-To: <BY5PR11MB3926FBF6B26CA3482B51F667CE85A@BY5PR11MB3926.namprd11.prod.outlook.com>
References: <BY5PR11MB3926FBF6B26CA3482B51F667CE85A@BY5PR11MB3926.namprd11.prod.outlook.com>
Message-ID: <SN6PR17MB2096D133CC42D0CF01C46307D985A@SN6PR17MB2096.namprd17.prod.outlook.com>

Hi Liz,

In the ArchivesSpace sandbox, I had to reload the webpage in order for changes made on the staff interface to show up on the public interface.

If that doesn't work, could the issue be related to the save/refresh rate of whatever is hosting your ArchivesSpace instance?

Best,
Courtney Rookard (she/her) | Processing Archivist
The National WWII Museum
New Orleans, LA
504-528-1944  x532

From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Liz Neely
Sent: Tuesday, December 05, 2023 11:38
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Determining which AO notes are published to the PUI (?)

You don't often get email from lneely at okeeffemuseum.org<mailto:lneely at okeeffemuseum.org>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
EXTERNAL EMAIL. This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Hello,

We are experimenting with using a Related Materials note to include the link to a record in another system that gives access to the related digital materials. I published both the note and subnote, but they are not showing up on the archival object record in the PUI.

I'm testing this with ArchivesSpace 3.4.1.

This is a note type 'Related Materials' with a label of View Digital Materials. In the subnote I include the HTML for the link. Both are published.

[cid:image001.png at 01DA2772.C388FA20]

But in the PUI, I only see the Ownership and Rights and Explanation of Rights notes. Is there a way that I can have all published notes show on this record? I looked in the config.db but didn't see anything at this level of specificity.

[A screenshot of a computer  Description automatically generated]

Any advice would be greatly appreciated!

Thank you,
Liz


Liz Neely (she/her)
Curator of Digital Experience
Georgia O'Keeffe Museum
Santa Fe, New Mexico
lneely at gokm.org<mailto:lneely at gokm.org>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231205/6f28ae51/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 408598 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231205/6f28ae51/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 55178 bytes
Desc: image002.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231205/6f28ae51/attachment-0001.png>

From snewhouse at sciencehistory.org  Tue Dec  5 13:09:11 2023
From: snewhouse at sciencehistory.org (Newhouse, Sarah)
Date: Tue, 5 Dec 2023 18:09:11 +0000
Subject: [Archivesspace_Users_Group]
 =?windows-1252?q?Digital_Objects_=96_?=
 =?windows-1252?q?examples_of_ASpace_records_+_repository_objects=3F?=
In-Reply-To: <BN9PR03MB59794A86E5FCB36879F0C5FDF085A@BN9PR03MB5979.namprd03.prod.outlook.com>
References: <BN9PR03MB59794A86E5FCB36879F0C5FDF085A@BN9PR03MB5979.namprd03.prod.outlook.com>
 <0bc9ca69-de9a-4006-bb1e-b786269e2036.5bc9e4a4-201a-4113-8500-06887445b2b4.06ee5d14-4db3-46b0-923e-d6ef5ea1d4d2@emailsignatures365.codetwo.com>
 <0bc9ca69-de9a-4006-bb1e-b786269e2036.1fe061b8-c04b-4022-ab6c-ea3cb89cd359.c1aefc88-c79b-4b8b-bccc-2415134842fa@emailsignatures365.codetwo.com>
Message-ID: <BN0PR20MB3877616E8FD44117680B6E44D385A@BN0PR20MB3877.namprd20.prod.outlook.com>

Morgan,

We've been putting off a similar discussion for a while now, because of all the reasons you've already outlined.

We initially tried using the DAO component for access, to link our ASpace PUI with our digital collections, but ran into issues with differing levels of description between the PUI and our DC. Specifically, a few large collections that had grant-funded digitization to scan and create item-level records in the DC for everything. So a folder or volume/item-level component in ASpace would have 100+ DAOs linked to it, which made for a really unhelpful PUI experience for users looking at that component with just an endless vertical scroll of DAOs.

Our longer-term solution is to look not at ASpace, but at the data in our DC and see if there's a way we can create or simulate folder or volume-level works for relevant items in the DC and link to those using the ASpace DAOs, so there's one DAO for one ASpace component (folder, volume, box, what have you). Luckily, when the DC was built (before ASpace adoption) the developers built in a field for physical location that records box, folder, and volume info (scroll down, under "Institutional location"): https://digital.sciencehistory.org/works/k0lxixk

Our interim solution is to use the Existence and Location of Copies note and link to collection-level works in our DC. Example here: https://archives.sciencehistory.org/repositories/3/resources/635

Happy to talk more over Zoom or email if more details would be helpful! We're a small library just trying to make access as easy as possible with the tools we've got.


Science History Institute
Chemistry ? Engineering ? Life Sciences
315 Chestnut Street ? Philadelphia, PA 19106 ? U.S.A.
We tell the stories behind the science.
sciencehistory.org<https://www.sciencehistory.org>

__________________________________

Sarah Newhouse   (she, her, hers)
Digital Preservation Archivist
Othmer Library of Chemical History
t. +1.215.873.8249

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of McKeehan, Morgan <morganem at live.unc.edu>
Sent: Tuesday, December 5, 2023 10:42 AM
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Digital Objects ? examples of ASpace records + repository objects?

Hi everyone,

I?m looking for examples of how other institutions have handled relationships between ASpace records and digital repository content, in cases when the physical arrangement vs. intellectual arrangement poses object-modeling challenges for digitized representations.

For example, in your systems do you have scenarios when an ASpace archival object record may have many ASpace digital object (DO) records linked to it, with each DO record corresponding to an individual object in your digital repository system? Conversely, perhaps there are also  situations where a single digital repository object contains files/digitized pages that are described by separate archival object records ? ie, a folder of stuff that was digitized as one grouping, but actually corresponds to more than one individual descriptive component?

At my institution, we?re working through these issues as we?re migrating our digitized materials to a new digital repository system at the same time as we?re also migrating our finding aids/archival data to ASpace. We would welcome any examples that others can share, in case you may have approaches from what has worked well, or lessons learned about what to avoid.

Please also feel free to message me off-list if more context or clarification about what I?m asking would be helpful. I?m happy to discuss more about our workflows and object modeling plans so far.

I?d also be happy to set up a zoom call if anyone has examples to share that it would be easier to walk through via zoom. I totally understand there may be examples that just seem too complicated to try to explain in an email!

Here's a little more explanation about the kinds of linking situations I?m asking about:

In our new digital repository, we plan to model digitized materials as repository objects based on the physical containers. For example, all digitized pages from a folder of correspondence would equal 1 repository object (a ?Work?). The URL of the repository object will provide the File Version value for an ASpace Digital Object record, and that DO record will be linked to the relevant archival object record that contains the description for the original materials.

In cases such as a grouping of documents that is housed in a range of physical folders, this will mean many DO records linked to an archival object record. A common scenario is something like: a descriptive component with Title: ?Correspondence, 1800?, housed in ?Folders 65-75?. This arrangement will give us 11 DO records linked to the ?Correspondence, 1800? archival object record. In many cases, folder ranges will be even larger, so there could easily be 20-30 or more DO records linked to an AO record. However, if we instead modeled all scans from Folders 65-75 as 1 object in our digital repository, since each folder contains 100+ pages, that arrangement would be a large and cumbersome repository object for users to navigate. Neither option seems great. We?re interested in learning about how others handle these types of situations!

Thanks for any examples or insights you can share,

Morgan

------------------------
Morgan McKeehan (she/her/hers)
Digital Collections Specialist
University Libraries
The University of North Carolina at Chapel Hill
morganem at email.unc.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231205/cfa9ce47/attachment.html>

From vaddonizio at atlas-sys.com  Tue Dec  5 14:13:55 2023
From: vaddonizio at atlas-sys.com (Valerie Addonizio)
Date: Tue, 5 Dec 2023 19:13:55 +0000
Subject: [Archivesspace_Users_Group] Determining which AO notes
	are	published to the PUI (?)
In-Reply-To: <BY5PR11MB3926FBF6B26CA3482B51F667CE85A@BY5PR11MB3926.namprd11.prod.outlook.com>
References: <BY5PR11MB3926FBF6B26CA3482B51F667CE85A@BY5PR11MB3926.namprd11.prod.outlook.com>
Message-ID: <MN2PR20MB22397C9D1DD0BADC327EBE3D8985A@MN2PR20MB2239.namprd20.prod.outlook.com>

Hi Liz,

This is a shot in the dark, but try including some text in addition to the link, as a test.

From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Liz Neely
Sent: Tuesday, December 5, 2023 12:38 PM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Determining which AO notes are published to the PUI (?)

Hello,

We are experimenting with using a Related Materials note to include the link to a record in another system that gives access to the related digital materials. I published both the note and subnote, but they are not showing up on the archival object record in the PUI.

I'm testing this with ArchivesSpace 3.4.1.

This is a note type 'Related Materials' with a label of View Digital Materials. In the subnote I include the HTML for the link. Both are published.

[cid:image001.png at 01DA2785.466552B0]

But in the PUI, I only see the Ownership and Rights and Explanation of Rights notes. Is there a way that I can have all published notes show on this record? I looked in the config.db but didn't see anything at this level of specificity.

[A screenshot of a computer  Description automatically generated]

Any advice would be greatly appreciated!

Thank you,
Liz


Liz Neely (she/her)
Curator of Digital Experience
Georgia O'Keeffe Museum
Santa Fe, New Mexico
lneely at gokm.org<mailto:lneely at gokm.org>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231205/7e0a277c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 408598 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231205/7e0a277c/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 55178 bytes
Desc: image002.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231205/7e0a277c/attachment-0003.png>

From w.hamill at auckland.ac.nz  Tue Dec  5 14:55:20 2023
From: w.hamill at auckland.ac.nz (William Hamill)
Date: Tue, 5 Dec 2023 19:55:20 +0000
Subject: [Archivesspace_Users_Group] Bulk import of DOs with multiple file
	versions
Message-ID: <MEYPR01MB73402B89CA95834628EF9531A385A@MEYPR01MB7340.ausprd01.prod.outlook.com>

Kia ora koutou,

I?m hoping someone out there may be able to offer some pointers on doing a bulk import of Digital Object records.

Using the aspace_digital_object_template.csv works fine as it is, but the records I would like to create typically have 2-3 file versions. I?ve tried copying the file version columns and adding ?_1? and ?_2? to various places, but the importer just skips those columns altogether and I get a record with no file versions at all.

Is this just a case of user error, or does the import template not work with multiple file versions? We?re running AS ver.3.3.1

Note that I?m just wanting to create the digital objects at this stage ? not import associating with an archival object (also, that importer seems to just have linked out object and thumbnail settings that don?t suit).

Any tips would be great,

Thanks very much

William Hamill
Team Leader ? Cultural Collections
Archive of M?ori and Pacific Sound
Te Tumu Herenga | Libraries and Learning Services
Waipapa Taumata Rau | University of Auckland
w.hamill at auckland.ac.nz<mailto:w.hamill at auckland.ac.nz>
Ph: (64 9) 373 7599 ext. 85733
DDI: (64 9) 923 5733

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231205/a4f97a19/attachment.html>

From kmc35 at psu.edu  Tue Dec  5 15:05:28 2023
From: kmc35 at psu.edu (Clair, Kevin)
Date: Tue, 5 Dec 2023 20:05:28 +0000
Subject: [Archivesspace_Users_Group]
 =?windows-1252?q?Digital_Objects_=96_?=
 =?windows-1252?q?examples_of_ASpace_records_+_repository_objects=3F?=
In-Reply-To: <BN0PR20MB3877616E8FD44117680B6E44D385A@BN0PR20MB3877.namprd20.prod.outlook.com>
References: <BN9PR03MB59794A86E5FCB36879F0C5FDF085A@BN9PR03MB5979.namprd03.prod.outlook.com>
 <0bc9ca69-de9a-4006-bb1e-b786269e2036.5bc9e4a4-201a-4113-8500-06887445b2b4.06ee5d14-4db3-46b0-923e-d6ef5ea1d4d2@emailsignatures365.codetwo.com>
 <0bc9ca69-de9a-4006-bb1e-b786269e2036.1fe061b8-c04b-4022-ab6c-ea3cb89cd359.c1aefc88-c79b-4b8b-bccc-2415134842fa@emailsignatures365.codetwo.com>
 <BN0PR20MB3877616E8FD44117680B6E44D385A@BN0PR20MB3877.namprd20.prod.outlook.com>
Message-ID: <IA1PR02MB94660DD0567B799F055770F4B585A@IA1PR02MB9466.namprd02.prod.outlook.com>

It's my favorite ArchivesSpace question!

I've managed this a couple of different ways. When I worked at the University of Denver we had (well, presumably they still have) a home-grown digital asset management system that relied entirely on ArchivesSpace as the metadata system of record. For that we assumed that every object in the digital repository also had a metadata record in ArchivesSpace, and we used the update-feed API endpoint to communicate when new digital objects had been created or existing ones had been updated so that the repository would reindex. I'm sure somewhere I still have my documentation of how that data model worked and can forward it to you if it's of interest, with the caveat that I left DU four years ago and I don't know how much it has changed in the meantime.

Here at Penn State, our digital object guidelines state that every item in our repository should have a unique identifier, which for bibliographic materials is its OCLC number and for archival materials is based on the ArchivesSpace reference ID. We've found, as Sarah described, that this poses problems with older digital collections that were published before we had guidelines, where their source collections are processed at the folder level but the digital collection is published at the item level. How we handle that varies based on the collection. Sometimes we will re-publish the digital collection to reflect the arrangement of the archival collection; more rarely, we will maintain the digital collection as it is and re-arrange the archival collection to reflect CONTENTdm. Ideally we want to be at the point where we have a strict 1:1 relationship between archival object and DAO records in ArchivesSpace. (Technically 1:2, because we manage access and preservation digital objects separately.)

We considered and abandoned the One Item, Many DAOs approach Sarah describes, although if you know where to look in our PUI you can definitely still find some examples of it...

Happy to talk more about this and/or share documentation, although I feel like our documentation is probably inadequate (isn't it always, though?).

cheers
-kevin

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Newhouse, Sarah <snewhouse at sciencehistory.org>
Sent: Tuesday, December 5, 2023 1:09 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Digital Objects ? examples of ASpace records + repository objects?

Morgan,

We've been putting off a similar discussion for a while now, because of all the reasons you've already outlined.

We initially tried using the DAO component for access, to link our ASpace PUI with our digital collections, but ran into issues with differing levels of description between the PUI and our DC. Specifically, a few large collections that had grant-funded digitization to scan and create item-level records in the DC for everything. So a folder or volume/item-level component in ASpace would have 100+ DAOs linked to it, which made for a really unhelpful PUI experience for users looking at that component with just an endless vertical scroll of DAOs.

Our longer-term solution is to look not at ASpace, but at the data in our DC and see if there's a way we can create or simulate folder or volume-level works for relevant items in the DC and link to those using the ASpace DAOs, so there's one DAO for one ASpace component (folder, volume, box, what have you). Luckily, when the DC was built (before ASpace adoption) the developers built in a field for physical location that records box, folder, and volume info (scroll down, under "Institutional location"): https://digital.sciencehistory.org/works/k0lxixk

Our interim solution is to use the Existence and Location of Copies note and link to collection-level works in our DC. Example here: https://archives.sciencehistory.org/repositories/3/resources/635

Happy to talk more over Zoom or email if more details would be helpful! We're a small library just trying to make access as easy as possible with the tools we've got.


Science History Institute
Chemistry ? Engineering ? Life Sciences
315 Chestnut Street ? Philadelphia, PA 19106 ? U.S.A.
We tell the stories behind the science.
sciencehistory.org<https://www.sciencehistory.org/>

__________________________________

Sarah Newhouse   (she, her, hers)
Digital Preservation Archivist
Othmer Library of Chemical History
t. +1.215.873.8249

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of McKeehan, Morgan <morganem at live.unc.edu>
Sent: Tuesday, December 5, 2023 10:42 AM
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Digital Objects ? examples of ASpace records + repository objects?

Hi everyone,

I?m looking for examples of how other institutions have handled relationships between ASpace records and digital repository content, in cases when the physical arrangement vs. intellectual arrangement poses object-modeling challenges for digitized representations.

For example, in your systems do you have scenarios when an ASpace archival object record may have many ASpace digital object (DO) records linked to it, with each DO record corresponding to an individual object in your digital repository system? Conversely, perhaps there are also  situations where a single digital repository object contains files/digitized pages that are described by separate archival object records ? ie, a folder of stuff that was digitized as one grouping, but actually corresponds to more than one individual descriptive component?

At my institution, we?re working through these issues as we?re migrating our digitized materials to a new digital repository system at the same time as we?re also migrating our finding aids/archival data to ASpace. We would welcome any examples that others can share, in case you may have approaches from what has worked well, or lessons learned about what to avoid.

Please also feel free to message me off-list if more context or clarification about what I?m asking would be helpful. I?m happy to discuss more about our workflows and object modeling plans so far.

I?d also be happy to set up a zoom call if anyone has examples to share that it would be easier to walk through via zoom. I totally understand there may be examples that just seem too complicated to try to explain in an email!

Here's a little more explanation about the kinds of linking situations I?m asking about:

In our new digital repository, we plan to model digitized materials as repository objects based on the physical containers. For example, all digitized pages from a folder of correspondence would equal 1 repository object (a ?Work?). The URL of the repository object will provide the File Version value for an ASpace Digital Object record, and that DO record will be linked to the relevant archival object record that contains the description for the original materials.

In cases such as a grouping of documents that is housed in a range of physical folders, this will mean many DO records linked to an archival object record. A common scenario is something like: a descriptive component with Title: ?Correspondence, 1800?, housed in ?Folders 65-75?. This arrangement will give us 11 DO records linked to the ?Correspondence, 1800? archival object record. In many cases, folder ranges will be even larger, so there could easily be 20-30 or more DO records linked to an AO record. However, if we instead modeled all scans from Folders 65-75 as 1 object in our digital repository, since each folder contains 100+ pages, that arrangement would be a large and cumbersome repository object for users to navigate. Neither option seems great. We?re interested in learning about how others handle these types of situations!

Thanks for any examples or insights you can share,

Morgan

------------------------
Morgan McKeehan (she/her/hers)
Digital Collections Specialist
University Libraries
The University of North Carolina at Chapel Hill
morganem at email.unc.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231205/a9987333/attachment.html>

From morganem at live.unc.edu  Tue Dec  5 17:18:08 2023
From: morganem at live.unc.edu (McKeehan, Morgan)
Date: Tue, 5 Dec 2023 22:18:08 +0000
Subject: [Archivesspace_Users_Group]
 =?windows-1252?q?Digital_Objects_=96_?=
 =?windows-1252?q?examples_of_ASpace_records_+_repository_objects=3F?=
In-Reply-To: <IA1PR02MB94660DD0567B799F055770F4B585A@IA1PR02MB9466.namprd02.prod.outlook.com>
References: <BN9PR03MB59794A86E5FCB36879F0C5FDF085A@BN9PR03MB5979.namprd03.prod.outlook.com>
 <0bc9ca69-de9a-4006-bb1e-b786269e2036.5bc9e4a4-201a-4113-8500-06887445b2b4.06ee5d14-4db3-46b0-923e-d6ef5ea1d4d2@emailsignatures365.codetwo.com>
 <0bc9ca69-de9a-4006-bb1e-b786269e2036.1fe061b8-c04b-4022-ab6c-ea3cb89cd359.c1aefc88-c79b-4b8b-bccc-2415134842fa@emailsignatures365.codetwo.com>
 <BN0PR20MB3877616E8FD44117680B6E44D385A@BN0PR20MB3877.namprd20.prod.outlook.com>
 <IA1PR02MB94660DD0567B799F055770F4B585A@IA1PR02MB9466.namprd02.prod.outlook.com>
Message-ID: <BN9PR03MB59794FED90D7CD980F3465EEF085A@BN9PR03MB5979.namprd03.prod.outlook.com>

Thank you for all the responses to this question! It's a huge help seeing the range of examples y'all have provided.

I will reach out to folks individually with followup questions. Just wanted to send a big thanks for all the time and thought folks put into sharing examples. We really appreciate it!

Morgan

------------------------
Morgan McKeehan (she/her/hers)
Digital Collections Specialist
University Libraries
The University of North Carolina at Chapel Hill
morganem at email.unc.edu
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Clair, Kevin <kmc35 at psu.edu>
Sent: Tuesday, December 5, 2023 15:05
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Digital Objects ? examples of ASpace records + repository objects?

You don't often get email from kmc35 at psu.edu. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
It's my favorite ArchivesSpace question!

I've managed this a couple of different ways. When I worked at the University of Denver we had (well, presumably they still have) a home-grown digital asset management system that relied entirely on ArchivesSpace as the metadata system of record. For that we assumed that every object in the digital repository also had a metadata record in ArchivesSpace, and we used the update-feed API endpoint to communicate when new digital objects had been created or existing ones had been updated so that the repository would reindex. I'm sure somewhere I still have my documentation of how that data model worked and can forward it to you if it's of interest, with the caveat that I left DU four years ago and I don't know how much it has changed in the meantime.

Here at Penn State, our digital object guidelines state that every item in our repository should have a unique identifier, which for bibliographic materials is its OCLC number and for archival materials is based on the ArchivesSpace reference ID. We've found, as Sarah described, that this poses problems with older digital collections that were published before we had guidelines, where their source collections are processed at the folder level but the digital collection is published at the item level. How we handle that varies based on the collection. Sometimes we will re-publish the digital collection to reflect the arrangement of the archival collection; more rarely, we will maintain the digital collection as it is and re-arrange the archival collection to reflect CONTENTdm. Ideally we want to be at the point where we have a strict 1:1 relationship between archival object and DAO records in ArchivesSpace. (Technically 1:2, because we manage access and preservation digital objects separately.)

We considered and abandoned the One Item, Many DAOs approach Sarah describes, although if you know where to look in our PUI you can definitely still find some examples of it...

Happy to talk more about this and/or share documentation, although I feel like our documentation is probably inadequate (isn't it always, though?).

cheers
-kevin

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Newhouse, Sarah <snewhouse at sciencehistory.org>
Sent: Tuesday, December 5, 2023 1:09 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Digital Objects ? examples of ASpace records + repository objects?

Morgan,

We've been putting off a similar discussion for a while now, because of all the reasons you've already outlined.

We initially tried using the DAO component for access, to link our ASpace PUI with our digital collections, but ran into issues with differing levels of description between the PUI and our DC. Specifically, a few large collections that had grant-funded digitization to scan and create item-level records in the DC for everything. So a folder or volume/item-level component in ASpace would have 100+ DAOs linked to it, which made for a really unhelpful PUI experience for users looking at that component with just an endless vertical scroll of DAOs.

Our longer-term solution is to look not at ASpace, but at the data in our DC and see if there's a way we can create or simulate folder or volume-level works for relevant items in the DC and link to those using the ASpace DAOs, so there's one DAO for one ASpace component (folder, volume, box, what have you). Luckily, when the DC was built (before ASpace adoption) the developers built in a field for physical location that records box, folder, and volume info (scroll down, under "Institutional location"): https://digital.sciencehistory.org/works/k0lxixk

Our interim solution is to use the Existence and Location of Copies note and link to collection-level works in our DC. Example here: https://archives.sciencehistory.org/repositories/3/resources/635

Happy to talk more over Zoom or email if more details would be helpful! We're a small library just trying to make access as easy as possible with the tools we've got.


Science History Institute
Chemistry ? Engineering ? Life Sciences
315 Chestnut Street ? Philadelphia, PA 19106 ? U.S.A.
We tell the stories behind the science.
sciencehistory.org<https://www.sciencehistory.org/>

__________________________________

Sarah Newhouse   (she, her, hers)
Digital Preservation Archivist
Othmer Library of Chemical History
t. +1.215.873.8249

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of McKeehan, Morgan <morganem at live.unc.edu>
Sent: Tuesday, December 5, 2023 10:42 AM
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Digital Objects ? examples of ASpace records + repository objects?

Hi everyone,

I?m looking for examples of how other institutions have handled relationships between ASpace records and digital repository content, in cases when the physical arrangement vs. intellectual arrangement poses object-modeling challenges for digitized representations.

For example, in your systems do you have scenarios when an ASpace archival object record may have many ASpace digital object (DO) records linked to it, with each DO record corresponding to an individual object in your digital repository system? Conversely, perhaps there are also  situations where a single digital repository object contains files/digitized pages that are described by separate archival object records ? ie, a folder of stuff that was digitized as one grouping, but actually corresponds to more than one individual descriptive component?

At my institution, we?re working through these issues as we?re migrating our digitized materials to a new digital repository system at the same time as we?re also migrating our finding aids/archival data to ASpace. We would welcome any examples that others can share, in case you may have approaches from what has worked well, or lessons learned about what to avoid.

Please also feel free to message me off-list if more context or clarification about what I?m asking would be helpful. I?m happy to discuss more about our workflows and object modeling plans so far.

I?d also be happy to set up a zoom call if anyone has examples to share that it would be easier to walk through via zoom. I totally understand there may be examples that just seem too complicated to try to explain in an email!

Here's a little more explanation about the kinds of linking situations I?m asking about:

In our new digital repository, we plan to model digitized materials as repository objects based on the physical containers. For example, all digitized pages from a folder of correspondence would equal 1 repository object (a ?Work?). The URL of the repository object will provide the File Version value for an ASpace Digital Object record, and that DO record will be linked to the relevant archival object record that contains the description for the original materials.

In cases such as a grouping of documents that is housed in a range of physical folders, this will mean many DO records linked to an archival object record. A common scenario is something like: a descriptive component with Title: ?Correspondence, 1800?, housed in ?Folders 65-75?. This arrangement will give us 11 DO records linked to the ?Correspondence, 1800? archival object record. In many cases, folder ranges will be even larger, so there could easily be 20-30 or more DO records linked to an AO record. However, if we instead modeled all scans from Folders 65-75 as 1 object in our digital repository, since each folder contains 100+ pages, that arrangement would be a large and cumbersome repository object for users to navigate. Neither option seems great. We?re interested in learning about how others handle these types of situations!

Thanks for any examples or insights you can share,

Morgan

------------------------
Morgan McKeehan (she/her/hers)
Digital Collections Specialist
University Libraries
The University of North Carolina at Chapel Hill
morganem at email.unc.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231205/f52bac60/attachment.html>

From Scott.Renton at ed.ac.uk  Wed Dec  6 04:51:41 2023
From: Scott.Renton at ed.ac.uk (Scott Renton)
Date: Wed, 6 Dec 2023 09:51:41 +0000
Subject: [Archivesspace_Users_Group] Digital Objects navigation in v3
Message-ID: <AS8PR05MB76244A63F20D9AB76030287CBA84A@AS8PR05MB7624.eurprd05.prod.outlook.com>

Hi folks

Just about to put our main archives site up from v2.8.1 to v3.4.1. One of our archivists has noticed that where, in the past, she was able to link directly from an image to its source in a native system

(eg https://archives.collections.ed.ac.uk/repositories/2/archival_objects/141060 - the link goes to search results in the LUNA image management system)

she is now forced to go to the digital object first, meaning there's a second click to get there.

Looking at the code, my feeling is that this is a very conscious method of routing in version 3, and it is not something we should look to change (I wouldn't even think the native link is even available to the controller, but rather the digital object id). However, I did think we should check to see if anyone in the community has hit a similar use case and taken any action before we communicate that this is the correct way to work now.

Thanks very much
Scott

PS my colleague Patryk (cc'd) has an outstanding request to register onto the list using the http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group - he's not been accepted in yet though- this is still the way to register?




==========

Scott Renton

Digital Library Development & Systems

Floor F East

Argyle House

515219

The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. Is e buidheann carthannais a th' ann an Oilthigh Dh?n ?ideann, cl?raichte an Alba, ?ireamh cl?raidh SC005336.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231206/f454ced1/attachment.html>

From dkloiber at conncoll.edu  Wed Dec  6 09:22:20 2023
From: dkloiber at conncoll.edu (Deborah Kloiber)
Date: Wed, 6 Dec 2023 09:22:20 -0500
Subject: [Archivesspace_Users_Group] Determining which AO notes are
 published to the PUI (?)
In-Reply-To: <BY5PR11MB3926FBF6B26CA3482B51F667CE85A@BY5PR11MB3926.namprd11.prod.outlook.com>
References: <BY5PR11MB3926FBF6B26CA3482B51F667CE85A@BY5PR11MB3926.namprd11.prod.outlook.com>
Message-ID: <CAF-LMgWi2aDRMfxYqsWh53bnKkM_UOgh4qZ=oT0b6=b_DAy5kQ@mail.gmail.com>

Hi Liz,

External links can show up in the Related Materials note, or I suspect in
any type of note.  The problem you're having is the way you've constructed
the link.  In ArchivesSpace you need to use an "extref" tag instead of an
"a" tag.  For example:

The first journal, covering the Crozier's travels from the US to Japan and
China is held by the <extref href="
https://archiveswest.orbiscascade.org/ark:80444/xv675457">American Heritage
Center</extref> at the University of Wyoming.


You can see the active link in the PUI here
<https://aspace.conncoll.edu/repositories/2/archival_objects/3537>.

Best,
Deborah
_______________________________

Deborah Kloiber, M.S.I.S, CA, DAS
College Archivist
Linda Lear Center for Special Collections and Archives

*Connecticut College*
Shain Library
270 Mohegan Avenue
New London, CT  06320
860-439-2686
dkloiber at conncoll.edu

Lear Center <http://learcenter.conncoll.edu> | Archives
<https://www.conncoll.edu/information-services/libraries/libraries-locations/linda-lear-center-for-special-collections-and-arc/about-our-collections/college-archives/>


On Tue, Dec 5, 2023 at 12:37?PM Liz Neely <lneely at okeeffemuseum.org> wrote:

> Hello,
>
>
>
> We are experimenting with using a Related Materials note to include the
> link to a record in another system that gives access to the related digital
> materials. I published both the note and subnote, but they are not showing
> up on the archival object record in the PUI.
>
>
>
> I?m testing this with ArchivesSpace 3.4.1.
>
>
>
> This is a note type ?Related Materials? with a label of View Digital
> Materials. In the subnote I include the HTML for the link. Both are
> published.
>
>
>
>
>
> But in the PUI, I only see the Ownership and Rights and Explanation of
> Rights notes. Is there a way that I can have all published notes show on
> this record? I looked in the config.db but didn?t see anything at this
> level of specificity.
>
>
>
> [image: A screenshot of a computer Description automatically generated]
>
>
>
> Any advice would be greatly appreciated!
>
>
>
> Thank you,
>
> Liz
>
>
>
>
>
> *Liz Neely *(she/her)
> Curator of Digital Experience
> Georgia O?Keeffe Museum
>
> Santa Fe, New Mexico
>
> lneely at gokm.org
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231206/d66f0873/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 408598 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231206/d66f0873/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 55178 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231206/d66f0873/attachment-0001.png>

From Ron.VandenBranden at antwerpen.be  Wed Dec  6 09:51:14 2023
From: Ron.VandenBranden at antwerpen.be (Ron Van den Branden)
Date: Wed, 6 Dec 2023 14:51:14 +0000
Subject: [Archivesspace_Users_Group] how to add a new locale to
	ArchivesSpace?
Message-ID: <AM9PR02MB6915A0EFA9E9233D27C3C0A48884A@AM9PR02MB6915.eurprd02.prod.outlook.com>

Hi all,
We're in the process of customizing the ArchivesSpace (3.4.1) staff interface for use in a Dutch-speaking context. We would like to translate the back-end user interface to Dutch. So far, in order to gain speed, we've resorted to tweaking the en.yml localization files with Dutch labels. In the longer run, hijacking "English" for another language feels like a hack, though.
The documentation for "customizing text" at https://archivesspace.github.io/tech-docs/customization/locales.html  does mention where strings can be customized in current locales, but not how new locales can be added. Simply adding new locale files for new languages, with according names and language codes, at the right locations doesn't seem to do the trick:

  *   either the language is not being offered in the list of available languages
  *   when additionally the new language is specified explicitly in the config/config.rb file as AppConfig[:locale] = :nl , this yields following error at startup:

JSONModel::ValidationException: #<:ValidationException: {:errors=>{"defaults/locale"=>["Invalid value 'nl'.  Must be one of: en, fr, de, ja, es"]}}>

                      validate at uri:classloader:/jsonmodel_type.rb:385

            with_validator_for at uri:classloader:/validator_cache.rb:41

...so there must be more to adding a new locale. Yet, we can't find where in the ArchivesSpace distribution code such a list of default locales can be found or edited.
We did find the file in the ArchivesSpace source tree at https://github.com/archivesspace/archivesspace/blob/master/common/aspace_i18n.rb#L28 which defines above list of locales This file can't be found in the distribution code, however, so it's not clear how it relates to the distribution code. The commit history also shows commits from the Weblate project at https://hosted.weblate.org/projects/archivesspace-interfaces/#languages, which contains additional languages Portuguese and Italian.
This leads to following questions:

  *   what's the mechanism for adding a new locale to an ArchivesSpace instance?
  *   if our translations would reach a stage of being of broader interest, what would be the procedure for contributing them?

Kind regards,
Ron


Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis

Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving |  Boeken en Letteren

Minderbroedersstraat 22, 2000 Antwerpen

Grote Markt 1, 2000 Antwerpen

gsm +32 0485 02 80 50 | tel. +32 3 222 93 30

letterenhuis.be<http://www.letterenhuis.be/> | instagram<https://www.instagram.com/letterenhuis/> | facebook<https://www.facebook.com/Letterenhuis>



Proclaimer

Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, niet voor u bestemd is, vragen we u vriendelijk om dat te melden aan de afzender. Deze e-mail en de bijlagen zijn namelijk offici?le documenten van de stad Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie bevatten. Als stad nemen we privacy heel serieus en willen we als een goede huisvader waken over de vertrouwelijkheid van documenten. Als u dit bericht per vergissing hebt ontvangen of ergens hebt gevonden, wees dan zo eerlijk om het meteen te verwijderen en het niet verder te verspreiden of te kopi?ren.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231206/9ab3101f/attachment-0001.html>

From christine.dibella at lyrasis.org  Wed Dec  6 10:42:05 2023
From: christine.dibella at lyrasis.org (Christine Di Bella)
Date: Wed, 6 Dec 2023 15:42:05 +0000
Subject: [Archivesspace_Users_Group] how to add a new locale
	to	ArchivesSpace?
In-Reply-To: <AM9PR02MB6915A0EFA9E9233D27C3C0A48884A@AM9PR02MB6915.eurprd02.prod.outlook.com>
References: <AM9PR02MB6915A0EFA9E9233D27C3C0A48884A@AM9PR02MB6915.eurprd02.prod.outlook.com>
Message-ID: <MN2PR22MB1887D0E3CF6329D21613A5F9F184A@MN2PR22MB1887.namprd22.prod.outlook.com>

Hello Ron,

It's great to hear that you're working on customizing your interfaces to have the option of providing labels in Dutch. I believe there are some institutions in the Netherlands, Belgium, and Luxembourg that have already done that, and you may hear from them here or directly. That would likely give you a very significant head start on your customization.

The Dutch translations themselves have not been contributed to the core ArchivesSpace yet, but we would be very interested in having them. We have a few options for contributing translations to ArchivesSpace, including using the Weblate service. If you are comfortable working directly with the .yml files, however, you need to first grab the ones from our GitHub repository itself. If you only use the ones in a release distribution file, your interface will be only partially translated.

These are the six directories to look for:
https://github.com/archivesspace/archivesspace/tree/master/common/locales
https://github.com/archivesspace/archivesspace/tree/master/common/locales/enums
https://github.com/archivesspace/archivesspace/tree/master/frontend/config/locales
https://github.com/archivesspace/archivesspace/tree/master/frontend/config/locales/help
https://github.com/archivesspace/archivesspace/tree/master/public/config/locales

https://github.com/archivesspace/archivesspace/tree/master/reports (there are locale files for each of the reports in the subdirectories under this main directory)

It's probably easiest to use the en.yml ones as your starting point since the labels in the file (the text that appears before the colons) need to stay in English. Follow the pattern you see and make a set where each file is named nl.yml. Within the files, change the text that appears after the colon for each entry you want to be in Dutch. (Don't change any of the formatting or line spacing since a computer is very literal.)

Once you've made all the changes you want, you can pull request the new files to us via GitHub, we can review, and then when all is correct and working like it should we will include them in a future release of ArchivesSpace.

There's plenty more to say, but I'll start there and see if anyone who's currently working with a translated interface or with translations has advice to offer. We're always interested in people submitting more languages for the ArchivesSpace application or improving the ones we have.

Christine

Christine Di Bella
ArchivesSpace Senior Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>

[cid:image001.jpg at 01DA282F.D73F8850]



From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Ron Van den Branden
Sent: Wednesday, December 6, 2023 9:51 AM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

Hi all,
We're in the process of customizing the ArchivesSpace (3.4.1) staff interface for use in a Dutch-speaking context. We would like to translate the back-end user interface to Dutch. So far, in order to gain speed, we've resorted to tweaking the en.yml localization files with Dutch labels. In the longer run, hijacking "English" for another language feels like a hack, though.
The documentation for "customizing text" at https://archivesspace.github.io/tech-docs/customization/locales.html  does mention where strings can be customized in current locales, but not how new locales can be added. Simply adding new locale files for new languages, with according names and language codes, at the right locations doesn't seem to do the trick:

  *   either the language is not being offered in the list of available languages
  *   when additionally the new language is specified explicitly in the config/config.rb file as AppConfig[:locale] = :nl , this yields following error at startup:

JSONModel::ValidationException: #<:ValidationException: {:errors=>{"defaults/locale"=>["Invalid value 'nl'.  Must be one of: en, fr, de, ja, es"]}}>

                      validate at uri:classloader:/jsonmodel_type.rb:385

            with_validator_for at uri:classloader:/validator_cache.rb:41
...so there must be more to adding a new locale. Yet, we can't find where in the ArchivesSpace distribution code such a list of default locales can be found or edited.
We did find the file in the ArchivesSpace source tree at https://github.com/archivesspace/archivesspace/blob/master/common/aspace_i18n.rb#L28 which defines above list of locales This file can't be found in the distribution code, however, so it's not clear how it relates to the distribution code. The commit history also shows commits from the Weblate project at https://hosted.weblate.org/projects/archivesspace-interfaces/#languages, which contains additional languages Portuguese and Italian.
This leads to following questions:

  *   what's the mechanism for adding a new locale to an ArchivesSpace instance?
  *   if our translations would reach a stage of being of broader interest, what would be the procedure for contributing them?
Kind regards,
Ron


Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis

Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving |  Boeken en Letteren

Minderbroedersstraat 22, 2000 Antwerpen

Grote Markt 1, 2000 Antwerpen

gsm +32 0485 02 80 50 | tel. +32 3 222 93 30

letterenhuis.be<http://www.letterenhuis.be/> | instagram<https://www.instagram.com/letterenhuis/> | facebook<https://www.facebook.com/Letterenhuis>



Proclaimer

Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, niet voor u bestemd is, vragen we u vriendelijk om dat te melden aan de afzender. Deze e-mail en de bijlagen zijn namelijk offici?le documenten van de stad Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie bevatten. Als stad nemen we privacy heel serieus en willen we als een goede huisvader waken over de vertrouwelijkheid van documenten. Als u dit bericht per vergissing hebt ontvangen of ergens hebt gevonden, wees dan zo eerlijk om het meteen te verwijderen en het niet verder te verspreiden of te kopi?ren.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231206/ffbce0b7/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 56099 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231206/ffbce0b7/attachment.jpg>

From Joshua.D.Shaw at dartmouth.edu  Wed Dec  6 10:44:20 2023
From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw)
Date: Wed, 6 Dec 2023 15:44:20 +0000
Subject: [Archivesspace_Users_Group] how to add a new locale
	to	ArchivesSpace?
In-Reply-To: <AM9PR02MB6915A0EFA9E9233D27C3C0A48884A@AM9PR02MB6915.eurprd02.prod.outlook.com>
References: <AM9PR02MB6915A0EFA9E9233D27C3C0A48884A@AM9PR02MB6915.eurprd02.prod.outlook.com>
Message-ID: <BL0PR03MB429285CBD09CD003B28C4F6AAB84A@BL0PR03MB4292.namprd03.prod.outlook.com>

Hey Ron

In addition to what Christine lists....

Off the top of my head (so take with a grain of salt since I haven't actually tested this!)...

In a plugin init (probably a backend plugin_init), monkey patch the self.supported_locales method in common/aspace_i18n.rb. Maybe something like

module I18n
def self.supported_locales
??????enhanced_locales = LOCALES

??????# map I18n language code => ArchivesSpace enumerations:language_iso639_2 code
??????# enumerations iso codes found in common/locales/enums
??????enhanced_locales['nl'] = 'dut'

??????enhanced_locales
end
end

Then you could add your new dutch locale file nl.yml within that same plugin.

OR

You could grab the code tree from github, patch it locally and build your patched application.

Both approaches have their own set of headaches as far as maintenance.

To contribute and other tech docs: https://archivesspace.github.io/tech-docs/readme_develop.html

Hope that helps!
Joshua



________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Ron Van den Branden <Ron.VandenBranden at antwerpen.be>
Sent: Wednesday, December 6, 2023 9:51 AM
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

Hi all,
We're in the process of customizing the ArchivesSpace (3.4.1) staff interface for use in a Dutch-speaking context. We would like to translate the back-end user interface to Dutch. So far, in order to gain speed, we've resorted to tweaking the en.yml localization files with Dutch labels. In the longer run, hijacking "English" for another language feels like a hack, though.
The documentation for "customizing text" at https://archivesspace.github.io/tech-docs/customization/locales.html  does mention where strings can be customized in current locales, but not how new locales can be added. Simply adding new locale files for new languages, with according names and language codes, at the right locations doesn't seem to do the trick:

  *   either the language is not being offered in the list of available languages
  *
when additionally the new language is specified explicitly in the config/config.rb file as AppConfig[:locale] = :nl , this yields following error at startup:

JSONModel::ValidationException: #<:ValidationException: {:errors=>{"defaults/locale"=>["Invalid value 'nl'.  Must be one of: en, fr, de, ja, es"]}}>

                      validate at uri:classloader:/jsonmodel_type.rb:385

            with_validator_for at uri:classloader:/validator_cache.rb:41

...so there must be more to adding a new locale. Yet, we can't find where in the ArchivesSpace distribution code such a list of default locales can be found or edited.
We did find the file in the ArchivesSpace source tree at https://github.com/archivesspace/archivesspace/blob/master/common/aspace_i18n.rb#L28 which defines above list of locales This file can't be found in the distribution code, however, so it's not clear how it relates to the distribution code. The commit history also shows commits from the Weblate project at https://hosted.weblate.org/projects/archivesspace-interfaces/#languages, which contains additional languages Portuguese and Italian.
This leads to following questions:

  *   what's the mechanism for adding a new locale to an ArchivesSpace instance?
  *   if our translations would reach a stage of being of broader interest, what would be the procedure for contributing them?

Kind regards,
Ron


Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis

Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving |  Boeken en Letteren

Minderbroedersstraat 22, 2000 Antwerpen

Grote Markt 1, 2000 Antwerpen

gsm +32 0485 02 80 50 | tel. +32 3 222 93 30

letterenhuis.be<http://www.letterenhuis.be/> | instagram<https://www.instagram.com/letterenhuis/> | facebook<https://www.facebook.com/Letterenhuis>



Proclaimer

Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, niet voor u bestemd is, vragen we u vriendelijk om dat te melden aan de afzender. Deze e-mail en de bijlagen zijn namelijk offici?le documenten van de stad Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie bevatten. Als stad nemen we privacy heel serieus en willen we als een goede huisvader waken over de vertrouwelijkheid van documenten. Als u dit bericht per vergissing hebt ontvangen of ergens hebt gevonden, wees dan zo eerlijk om het meteen te verwijderen en het niet verder te verspreiden of te kopi?ren.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231206/42baa32a/attachment.html>

From nrichbe at clemson.edu  Wed Dec  6 10:44:41 2023
From: nrichbe at clemson.edu (Nick Richbell)
Date: Wed, 6 Dec 2023 15:44:41 +0000
Subject: [Archivesspace_Users_Group] Export resource records to Excel
Message-ID: <SJ0PR06MB744011C2DC5995B982353247AC84A@SJ0PR06MB7440.namprd06.prod.outlook.com>

Good morning, List:

I am new to ArchivesSpace and am slowly figuring this out. One thing I need some help with is whether I can export a resource (all of the collection) to Excel? I've tried to find a solution but have had no success.

Any advice will be gratefully received!

Thanks, Nick



Nick Richbell, MLIS

Head, Special Collections and Archives

Clemson University Libraries

Clemson University



Strom Thurmond Institute

230 Kappa Street

Clemson, SC  29634

864-656-3875

http://libraries.clemson.edu/specialcollections/



 [cid:d0c8b886-eb4d-435a-9af7-567ee454a7f4]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231206/0a3cb8b5/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Outlook-r5hfgnmb.png
Type: image/png
Size: 3417 bytes
Desc: Outlook-r5hfgnmb.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231206/0a3cb8b5/attachment.png>

From Ron.VandenBranden at antwerpen.be  Wed Dec  6 10:57:06 2023
From: Ron.VandenBranden at antwerpen.be (Ron Van den Branden)
Date: Wed, 6 Dec 2023 15:57:06 +0000
Subject: [Archivesspace_Users_Group] how to add a new
	locale	to	ArchivesSpace?
In-Reply-To: <MN2PR22MB1887D0E3CF6329D21613A5F9F184A@MN2PR22MB1887.namprd22.prod.outlook.com>
References: <AM9PR02MB6915A0EFA9E9233D27C3C0A48884A@AM9PR02MB6915.eurprd02.prod.outlook.com>
 <MN2PR22MB1887D0E3CF6329D21613A5F9F184A@MN2PR22MB1887.namprd22.prod.outlook.com>
Message-ID: <AM9PR02MB691594E9CDA01556BCDC09F88884A@AM9PR02MB6915.eurprd02.prod.outlook.com>

Hi Christine,

Many thanks for your detailed answer, and the complete overview of where to look for localization files.

Editing the yml files (at least those under common and frontend) is exactly the approach we've taken. So far, with the "hack" of editing the translations in the en.yml files.

I appreciate including a new translation into the ArchivesSpace code would take some time and thourough review. What I'm missing, still, is an answer to the question whether it's possible in the meantime to "properly" add a new localization, and register those nl.yml files as a NL localization in an ArchivesSpace distribution. That would make it easier, IMO, to share and contribute those Dutch translation files in an earlier stage with potential interested parties, and offer them in a more mature stage for inclusion into ArchivesSpace.

Best,

Ron

________________________________
Van: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> namens Christine Di Bella <christine.dibella at lyrasis.org>
Verzonden: woensdag 6 december 2023 16:42
Aan: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Onderwerp: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?


WAARSCHUWING: DIT IS EEN EXTERNE MAIL

Deze mail komt van buiten onze organisatie. Kijk eerst of je het mailadres en de afzender herkent en/of vertrouwt. Doe dat voor je bijlagen opent of links aanklikt. Zo houden we onze organisatie veiliger voor phishing.

Hello Ron,



It?s great to hear that you?re working on customizing your interfaces to have the option of providing labels in Dutch. I believe there are some institutions in the Netherlands, Belgium, and Luxembourg that have already done that, and you may hear from them here or directly. That would likely give you a very significant head start on your customization.



The Dutch translations themselves have not been contributed to the core ArchivesSpace yet, but we would be very interested in having them. We have a few options for contributing translations to ArchivesSpace, including using the Weblate service. If you are comfortable working directly with the .yml files, however, you need to first grab the ones from our GitHub repository itself. If you only use the ones in a release distribution file, your interface will be only partially translated.



These are the six directories to look for:

https://github.com/archivesspace/archivesspace/tree/master/common/locales

https://github.com/archivesspace/archivesspace/tree/master/common/locales/enums

https://github.com/archivesspace/archivesspace/tree/master/frontend/config/locales

https://github.com/archivesspace/archivesspace/tree/master/frontend/config/locales/help

https://github.com/archivesspace/archivesspace/tree/master/public/config/locales



https://github.com/archivesspace/archivesspace/tree/master/reports (there are locale files for each of the reports in the subdirectories under this main directory)



It?s probably easiest to use the en.yml ones as your starting point since the labels in the file (the text that appears before the colons) need to stay in English. Follow the pattern you see and make a set where each file is named nl.yml. Within the files, change the text that appears after the colon for each entry you want to be in Dutch. (Don?t change any of the formatting or line spacing since a computer is very literal.)



Once you?ve made all the changes you want, you can pull request the new files to us via GitHub, we can review, and then when all is correct and working like it should we will include them in a future release of ArchivesSpace.



There?s plenty more to say, but I?ll start there and see if anyone who?s currently working with a translated interface or with translations has advice to offer. We?re always interested in people submitting more languages for the ArchivesSpace application or improving the ones we have.



Christine



Christine Di Bella

ArchivesSpace Senior Program Manager

christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>



[cid:image001.jpg at 01DA282F.D73F8850]







From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Ron Van den Branden
Sent: Wednesday, December 6, 2023 9:51 AM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?



Hi all,

We're in the process of customizing the ArchivesSpace (3.4.1) staff interface for use in a Dutch-speaking context. We would like to translate the back-end user interface to Dutch. So far, in order to gain speed, we've resorted to tweaking the en.yml localization files with Dutch labels. In the longer run, hijacking "English" for another language feels like a hack, though.

The documentation for "customizing text" at https://archivesspace.github.io/tech-docs/customization/locales.html  does mention where strings can be customized in current locales, but not how new locales can be added. Simply adding new locale files for new languages, with according names and language codes, at the right locations doesn't seem to do the trick:

  *   either the language is not being offered in the list of available languages
  *   when additionally the new language is specified explicitly in the config/config.rb file as AppConfig[:locale] = :nl , this yields following error at startup:

JSONModel::ValidationException: #<:ValidationException: {:errors=>{"defaults/locale"=>["Invalid value 'nl'.  Must be one of: en, fr, de, ja, es"]}}>

                      validate at uri:classloader:/jsonmodel_type.rb:385

            with_validator_for at uri:classloader:/validator_cache.rb:41

...so there must be more to adding a new locale. Yet, we can't find where in the ArchivesSpace distribution code such a list of default locales can be found or edited.

We did find the file in the ArchivesSpace source tree at https://github.com/archivesspace/archivesspace/blob/master/common/aspace_i18n.rb#L28 which defines above list of locales This file can't be found in the distribution code, however, so it's not clear how it relates to the distribution code. The commit history also shows commits from the Weblate project at https://hosted.weblate.org/projects/archivesspace-interfaces/#languages, which contains additional languages Portuguese and Italian.

This leads to following questions:

  *   what's the mechanism for adding a new locale to an ArchivesSpace instance?
  *   if our translations would reach a stage of being of broader interest, what would be the procedure for contributing them?

Kind regards,

Ron



Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis

Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving |  Boeken en Letteren

Minderbroedersstraat 22, 2000 Antwerpen

Grote Markt 1, 2000 Antwerpen

gsm +32 0485 02 80 50 | tel. +32 3 222 93 30

letterenhuis.be<http://www.letterenhuis.be/> | instagram<https://www.instagram.com/letterenhuis/> | facebook<https://www.facebook.com/Letterenhuis>



Proclaimer

Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, niet voor u bestemd is, vragen we u vriendelijk om dat te melden aan de afzender. Deze e-mail en de bijlagen zijn namelijk offici?le documenten van de stad Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie bevatten. Als stad nemen we privacy heel serieus en willen we als een goede huisvader waken over de vertrouwelijkheid van documenten. Als u dit bericht per vergissing hebt ontvangen of ergens hebt gevonden, wees dan zo eerlijk om het meteen te verwijderen en het niet verder te verspreiden of te kopi?ren.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231206/1a046d43/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 56099 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231206/1a046d43/attachment.jpg>

From Ron.VandenBranden at antwerpen.be  Wed Dec  6 11:01:51 2023
From: Ron.VandenBranden at antwerpen.be (Ron Van den Branden)
Date: Wed, 6 Dec 2023 16:01:51 +0000
Subject: [Archivesspace_Users_Group] how to add a new
	locale	to	ArchivesSpace?
In-Reply-To: <BL0PR03MB429285CBD09CD003B28C4F6AAB84A@BL0PR03MB4292.namprd03.prod.outlook.com>
References: <AM9PR02MB6915A0EFA9E9233D27C3C0A48884A@AM9PR02MB6915.eurprd02.prod.outlook.com>
 <BL0PR03MB429285CBD09CD003B28C4F6AAB84A@BL0PR03MB4292.namprd03.prod.outlook.com>
Message-ID: <AM9PR02MB6915C05D88CFCC135AC8CF138884A@AM9PR02MB6915.eurprd02.prod.outlook.com>

Hi Joshua,

Ok, thanks for that pointer! The point is that we couldn't find that common/aspace_i18n.rb file in the ArchivesSpace distribution code. Or are you suggesting to add it in a plugin? If so, would you mind guiding me a bit more?

I don't think we've succeeded in building from source (I'm on Windows, so I'm probably at a loss for local testing, I recall some Ruby build incompatibilities).

Best,

Ron

________________________________
Van: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> namens Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Verzonden: woensdag 6 december 2023 16:44
Aan: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Onderwerp: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

U ontvangt niet vaak e-mail van joshua.d.shaw at dartmouth.edu. Meer informatie over waarom dit belangrijk is<https://aka.ms/LearnAboutSenderIdentification>

WAARSCHUWING: DIT IS EEN EXTERNE MAIL

Deze mail komt van buiten onze organisatie. Kijk eerst of je het mailadres en de afzender herkent en/of vertrouwt. Doe dat voor je bijlagen opent of links aanklikt. Zo houden we onze organisatie veiliger voor phishing.

Hey Ron

In addition to what Christine lists....

Off the top of my head (so take with a grain of salt since I haven't actually tested this!)...

In a plugin init (probably a backend plugin_init), monkey patch the self.supported_locales method in common/aspace_i18n.rb. Maybe something like

module I18n
def self.supported_locales
??????enhanced_locales = LOCALES

??????# map I18n language code => ArchivesSpace enumerations:language_iso639_2 code
??????# enumerations iso codes found in common/locales/enums
??????enhanced_locales['nl'] = 'dut'

??????enhanced_locales
end
end

Then you could add your new dutch locale file nl.yml within that same plugin.

OR

You could grab the code tree from github, patch it locally and build your patched application.

Both approaches have their own set of headaches as far as maintenance.

To contribute and other tech docs: https://archivesspace.github.io/tech-docs/readme_develop.html

Hope that helps!
Joshua



________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Ron Van den Branden <Ron.VandenBranden at antwerpen.be>
Sent: Wednesday, December 6, 2023 9:51 AM
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

Hi all,
We're in the process of customizing the ArchivesSpace (3.4.1) staff interface for use in a Dutch-speaking context. We would like to translate the back-end user interface to Dutch. So far, in order to gain speed, we've resorted to tweaking the en.yml localization files with Dutch labels. In the longer run, hijacking "English" for another language feels like a hack, though.
The documentation for "customizing text" at https://archivesspace.github.io/tech-docs/customization/locales.html  does mention where strings can be customized in current locales, but not how new locales can be added. Simply adding new locale files for new languages, with according names and language codes, at the right locations doesn't seem to do the trick:

  *   either the language is not being offered in the list of available languages
  *
when additionally the new language is specified explicitly in the config/config.rb file as AppConfig[:locale] = :nl , this yields following error at startup:

JSONModel::ValidationException: #<:ValidationException: {:errors=>{"defaults/locale"=>["Invalid value 'nl'.  Must be one of: en, fr, de, ja, es"]}}>

                      validate at uri:classloader:/jsonmodel_type.rb:385

            with_validator_for at uri:classloader:/validator_cache.rb:41

...so there must be more to adding a new locale. Yet, we can't find where in the ArchivesSpace distribution code such a list of default locales can be found or edited.
We did find the file in the ArchivesSpace source tree at https://github.com/archivesspace/archivesspace/blob/master/common/aspace_i18n.rb#L28 which defines above list of locales This file can't be found in the distribution code, however, so it's not clear how it relates to the distribution code. The commit history also shows commits from the Weblate project at https://hosted.weblate.org/projects/archivesspace-interfaces/#languages, which contains additional languages Portuguese and Italian.
This leads to following questions:

  *   what's the mechanism for adding a new locale to an ArchivesSpace instance?
  *   if our translations would reach a stage of being of broader interest, what would be the procedure for contributing them?

Kind regards,
Ron


Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis

Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving |  Boeken en Letteren

Minderbroedersstraat 22, 2000 Antwerpen

Grote Markt 1, 2000 Antwerpen

gsm +32 0485 02 80 50 | tel. +32 3 222 93 30

letterenhuis.be<http://www.letterenhuis.be/> | instagram<https://www.instagram.com/letterenhuis/> | facebook<https://www.facebook.com/Letterenhuis>



Proclaimer

Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, niet voor u bestemd is, vragen we u vriendelijk om dat te melden aan de afzender. Deze e-mail en de bijlagen zijn namelijk offici?le documenten van de stad Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie bevatten. Als stad nemen we privacy heel serieus en willen we als een goede huisvader waken over de vertrouwelijkheid van documenten. Als u dit bericht per vergissing hebt ontvangen of ergens hebt gevonden, wees dan zo eerlijk om het meteen te verwijderen en het niet verder te verspreiden of te kopi?ren.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231206/196309b2/attachment.html>

From Joshua.D.Shaw at dartmouth.edu  Wed Dec  6 11:21:43 2023
From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw)
Date: Wed, 6 Dec 2023 16:21:43 +0000
Subject: [Archivesspace_Users_Group] how to add a
	new	locale	to	ArchivesSpace?
In-Reply-To: <AM9PR02MB6915C05D88CFCC135AC8CF138884A@AM9PR02MB6915.eurprd02.prod.outlook.com>
References: <AM9PR02MB6915A0EFA9E9233D27C3C0A48884A@AM9PR02MB6915.eurprd02.prod.outlook.com>
 <BL0PR03MB429285CBD09CD003B28C4F6AAB84A@BL0PR03MB4292.namprd03.prod.outlook.com>
 <AM9PR02MB6915C05D88CFCC135AC8CF138884A@AM9PR02MB6915.eurprd02.prod.outlook.com>
Message-ID: <BL0PR03MB429277DEAE0184082B3D4974AB84A@BL0PR03MB4292.namprd03.prod.outlook.com>

Hey Ron

Here's the way I'd do this.


  1.  Create a new directory in the plugin folder in your ArchivesSpace directory. Call it something like aspace_custom_locatizations (or whatever you want)
  2.  In that new directory, create two new directories: backend and frontend
  3.  In the backend directory, add a file called plugin_init.rb. Put the contents of the monkey patch in that file
  4.  In the frontend directory, add a file tree that mimics the locales directory in the core code:
     *   locales/
     *   locales/enums
  5.  Add your new dutch locales files to those two locations. Name them nl.yml
  6.  In your config file, add your plugin name (the directory name in step 1) to the list of plugins that are active: AppConfig[:plugins] is the key you want to edit.

Since I haven't tested this, there may be some gotchas I'm not thinking about as far as the monkeypatch and where the locales list may also be referenced, but this is the approach I'd take.

There's more info on that tech docs page and there are a bunch of examples to be found on the Awesome ArchivesSpace repo (https://github.com/archivesspace/awesome-archivesspace) and Hudson Molonglo's repos (https://github.com/hudmol) and https://gitlab.gaiaresources.com.au/explor<https://gitlab.gaiaresources.com.au/explore>

jds


________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Ron Van den Branden <Ron.VandenBranden at antwerpen.be>
Sent: Wednesday, December 6, 2023 11:01 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

Hi Joshua,

Ok, thanks for that pointer! The point is that we couldn't find that common/aspace_i18n.rb file in the ArchivesSpace distribution code. Or are you suggesting to add it in a plugin? If so, would you mind guiding me a bit more?

I don't think we've succeeded in building from source (I'm on Windows, so I'm probably at a loss for local testing, I recall some Ruby build incompatibilities).

Best,

Ron

________________________________
Van: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> namens Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Verzonden: woensdag 6 december 2023 16:44
Aan: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Onderwerp: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

U ontvangt niet vaak e-mail van joshua.d.shaw at dartmouth.edu. Meer informatie over waarom dit belangrijk is<https://aka.ms/LearnAboutSenderIdentification>

WAARSCHUWING: DIT IS EEN EXTERNE MAIL

Deze mail komt van buiten onze organisatie. Kijk eerst of je het mailadres en de afzender herkent en/of vertrouwt. Doe dat voor je bijlagen opent of links aanklikt. Zo houden we onze organisatie veiliger voor phishing.

Hey Ron

In addition to what Christine lists....

Off the top of my head (so take with a grain of salt since I haven't actually tested this!)...

In a plugin init (probably a backend plugin_init), monkey patch the self.supported_locales method in common/aspace_i18n.rb. Maybe something like

module I18n
def self.supported_locales
??????enhanced_locales = LOCALES

??????# map I18n language code => ArchivesSpace enumerations:language_iso639_2 code
??????# enumerations iso codes found in common/locales/enums
??????enhanced_locales['nl'] = 'dut'

??????enhanced_locales
end
end

Then you could add your new dutch locale file nl.yml within that same plugin.

OR

You could grab the code tree from github, patch it locally and build your patched application.

Both approaches have their own set of headaches as far as maintenance.

To contribute and other tech docs: https://archivesspace.github.io/tech-docs/readme_develop.html

Hope that helps!
Joshua



________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Ron Van den Branden <Ron.VandenBranden at antwerpen.be>
Sent: Wednesday, December 6, 2023 9:51 AM
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

Hi all,
We're in the process of customizing the ArchivesSpace (3.4.1) staff interface for use in a Dutch-speaking context. We would like to translate the back-end user interface to Dutch. So far, in order to gain speed, we've resorted to tweaking the en.yml localization files with Dutch labels. In the longer run, hijacking "English" for another language feels like a hack, though.
The documentation for "customizing text" at https://archivesspace.github.io/tech-docs/customization/locales.html  does mention where strings can be customized in current locales, but not how new locales can be added. Simply adding new locale files for new languages, with according names and language codes, at the right locations doesn't seem to do the trick:

  *   either the language is not being offered in the list of available languages
  *
when additionally the new language is specified explicitly in the config/config.rb file as AppConfig[:locale] = :nl , this yields following error at startup:

JSONModel::ValidationException: #<:ValidationException: {:errors=>{"defaults/locale"=>["Invalid value 'nl'.  Must be one of: en, fr, de, ja, es"]}}>

                      validate at uri:classloader:/jsonmodel_type.rb:385

            with_validator_for at uri:classloader:/validator_cache.rb:41

...so there must be more to adding a new locale. Yet, we can't find where in the ArchivesSpace distribution code such a list of default locales can be found or edited.
We did find the file in the ArchivesSpace source tree at https://github.com/archivesspace/archivesspace/blob/master/common/aspace_i18n.rb#L28 which defines above list of locales This file can't be found in the distribution code, however, so it's not clear how it relates to the distribution code. The commit history also shows commits from the Weblate project at https://hosted.weblate.org/projects/archivesspace-interfaces/#languages, which contains additional languages Portuguese and Italian.
This leads to following questions:

  *   what's the mechanism for adding a new locale to an ArchivesSpace instance?
  *   if our translations would reach a stage of being of broader interest, what would be the procedure for contributing them?

Kind regards,
Ron


Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis

Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving |  Boeken en Letteren

Minderbroedersstraat 22, 2000 Antwerpen

Grote Markt 1, 2000 Antwerpen

gsm +32 0485 02 80 50 | tel. +32 3 222 93 30

letterenhuis.be<http://www.letterenhuis.be/> | instagram<https://www.instagram.com/letterenhuis/> | facebook<https://www.facebook.com/Letterenhuis>



Proclaimer

Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, niet voor u bestemd is, vragen we u vriendelijk om dat te melden aan de afzender. Deze e-mail en de bijlagen zijn namelijk offici?le documenten van de stad Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie bevatten. Als stad nemen we privacy heel serieus en willen we als een goede huisvader waken over de vertrouwelijkheid van documenten. Als u dit bericht per vergissing hebt ontvangen of ergens hebt gevonden, wees dan zo eerlijk om het meteen te verwijderen en het niet verder te verspreiden of te kopi?ren.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231206/35231e6f/attachment.html>

From Ron.VandenBranden at antwerpen.be  Wed Dec  6 12:00:14 2023
From: Ron.VandenBranden at antwerpen.be (Ron Van den Branden)
Date: Wed, 6 Dec 2023 17:00:14 +0000
Subject: [Archivesspace_Users_Group] how to add
	a	new	locale	to	ArchivesSpace?
In-Reply-To: <BL0PR03MB429277DEAE0184082B3D4974AB84A@BL0PR03MB4292.namprd03.prod.outlook.com>
References: <AM9PR02MB6915A0EFA9E9233D27C3C0A48884A@AM9PR02MB6915.eurprd02.prod.outlook.com>
 <BL0PR03MB429285CBD09CD003B28C4F6AAB84A@BL0PR03MB4292.namprd03.prod.outlook.com>
 <AM9PR02MB6915C05D88CFCC135AC8CF138884A@AM9PR02MB6915.eurprd02.prod.outlook.com>
 <BL0PR03MB429277DEAE0184082B3D4974AB84A@BL0PR03MB4292.namprd03.prod.outlook.com>
Message-ID: <AM9PR02MB6915C693049E3712B7F54CE48884A@AM9PR02MB6915.eurprd02.prod.outlook.com>

Hi Joshua,

Thanks again for your detailed steps! Although a first attempt didn't work (startup keeps choking on the original languages list), I'm sure we'll get there, with more time. Thanks for pointing me in the good direction: overriding the language list via plugin initialization. I'll definitely check out those other plugins for inspiration.

Best,

Ron


________________________________
Van: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> namens Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Verzonden: woensdag 6 december 2023 17:21
Aan: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Onderwerp: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

U ontvangt niet vaak e-mail van joshua.d.shaw at dartmouth.edu. Meer informatie over waarom dit belangrijk is<https://aka.ms/LearnAboutSenderIdentification>

WAARSCHUWING: DIT IS EEN EXTERNE MAIL

Deze mail komt van buiten onze organisatie. Kijk eerst of je het mailadres en de afzender herkent en/of vertrouwt. Doe dat voor je bijlagen opent of links aanklikt. Zo houden we onze organisatie veiliger voor phishing.

Hey Ron

Here's the way I'd do this.


  1.  Create a new directory in the plugin folder in your ArchivesSpace directory. Call it something like aspace_custom_locatizations (or whatever you want)
  2.  In that new directory, create two new directories: backend and frontend
  3.  In the backend directory, add a file called plugin_init.rb. Put the contents of the monkey patch in that file
  4.  In the frontend directory, add a file tree that mimics the locales directory in the core code:
     *   locales/
     *   locales/enums
  5.  Add your new dutch locales files to those two locations. Name them nl.yml
  6.  In your config file, add your plugin name (the directory name in step 1) to the list of plugins that are active: AppConfig[:plugins] is the key you want to edit.

Since I haven't tested this, there may be some gotchas I'm not thinking about as far as the monkeypatch and where the locales list may also be referenced, but this is the approach I'd take.

There's more info on that tech docs page and there are a bunch of examples to be found on the Awesome ArchivesSpace repo (https://github.com/archivesspace/awesome-archivesspace) and Hudson Molonglo's repos (https://github.com/hudmol) and https://gitlab.gaiaresources.com.au/explor<https://gitlab.gaiaresources.com.au/explore>

jds


________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Ron Van den Branden <Ron.VandenBranden at antwerpen.be>
Sent: Wednesday, December 6, 2023 11:01 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

Hi Joshua,

Ok, thanks for that pointer! The point is that we couldn't find that common/aspace_i18n.rb file in the ArchivesSpace distribution code. Or are you suggesting to add it in a plugin? If so, would you mind guiding me a bit more?

I don't think we've succeeded in building from source (I'm on Windows, so I'm probably at a loss for local testing, I recall some Ruby build incompatibilities).

Best,

Ron

________________________________
Van: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> namens Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Verzonden: woensdag 6 december 2023 16:44
Aan: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Onderwerp: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

U ontvangt niet vaak e-mail van joshua.d.shaw at dartmouth.edu. Meer informatie over waarom dit belangrijk is<https://aka.ms/LearnAboutSenderIdentification>

WAARSCHUWING: DIT IS EEN EXTERNE MAIL

Deze mail komt van buiten onze organisatie. Kijk eerst of je het mailadres en de afzender herkent en/of vertrouwt. Doe dat voor je bijlagen opent of links aanklikt. Zo houden we onze organisatie veiliger voor phishing.

Hey Ron

In addition to what Christine lists....

Off the top of my head (so take with a grain of salt since I haven't actually tested this!)...

In a plugin init (probably a backend plugin_init), monkey patch the self.supported_locales method in common/aspace_i18n.rb. Maybe something like

module I18n
def self.supported_locales
??????enhanced_locales = LOCALES

??????# map I18n language code => ArchivesSpace enumerations:language_iso639_2 code
??????# enumerations iso codes found in common/locales/enums
??????enhanced_locales['nl'] = 'dut'

??????enhanced_locales
end
end

Then you could add your new dutch locale file nl.yml within that same plugin.

OR

You could grab the code tree from github, patch it locally and build your patched application.

Both approaches have their own set of headaches as far as maintenance.

To contribute and other tech docs: https://archivesspace.github.io/tech-docs/readme_develop.html

Hope that helps!
Joshua



________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Ron Van den Branden <Ron.VandenBranden at antwerpen.be>
Sent: Wednesday, December 6, 2023 9:51 AM
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

Hi all,
We're in the process of customizing the ArchivesSpace (3.4.1) staff interface for use in a Dutch-speaking context. We would like to translate the back-end user interface to Dutch. So far, in order to gain speed, we've resorted to tweaking the en.yml localization files with Dutch labels. In the longer run, hijacking "English" for another language feels like a hack, though.
The documentation for "customizing text" at https://archivesspace.github.io/tech-docs/customization/locales.html  does mention where strings can be customized in current locales, but not how new locales can be added. Simply adding new locale files for new languages, with according names and language codes, at the right locations doesn't seem to do the trick:

  *   either the language is not being offered in the list of available languages
  *
when additionally the new language is specified explicitly in the config/config.rb file as AppConfig[:locale] = :nl , this yields following error at startup:

JSONModel::ValidationException: #<:ValidationException: {:errors=>{"defaults/locale"=>["Invalid value 'nl'.  Must be one of: en, fr, de, ja, es"]}}>

                      validate at uri:classloader:/jsonmodel_type.rb:385

            with_validator_for at uri:classloader:/validator_cache.rb:41

...so there must be more to adding a new locale. Yet, we can't find where in the ArchivesSpace distribution code such a list of default locales can be found or edited.
We did find the file in the ArchivesSpace source tree at https://github.com/archivesspace/archivesspace/blob/master/common/aspace_i18n.rb#L28 which defines above list of locales This file can't be found in the distribution code, however, so it's not clear how it relates to the distribution code. The commit history also shows commits from the Weblate project at https://hosted.weblate.org/projects/archivesspace-interfaces/#languages, which contains additional languages Portuguese and Italian.
This leads to following questions:

  *   what's the mechanism for adding a new locale to an ArchivesSpace instance?
  *   if our translations would reach a stage of being of broader interest, what would be the procedure for contributing them?

Kind regards,
Ron


Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis

Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving |  Boeken en Letteren

Minderbroedersstraat 22, 2000 Antwerpen

Grote Markt 1, 2000 Antwerpen

gsm +32 0485 02 80 50 | tel. +32 3 222 93 30

letterenhuis.be<http://www.letterenhuis.be/> | instagram<https://www.instagram.com/letterenhuis/> | facebook<https://www.facebook.com/Letterenhuis>



Proclaimer

Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, niet voor u bestemd is, vragen we u vriendelijk om dat te melden aan de afzender. Deze e-mail en de bijlagen zijn namelijk offici?le documenten van de stad Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie bevatten. Als stad nemen we privacy heel serieus en willen we als een goede huisvader waken over de vertrouwelijkheid van documenten. Als u dit bericht per vergissing hebt ontvangen of ergens hebt gevonden, wees dan zo eerlijk om het meteen te verwijderen en het niet verder te verspreiden of te kopi?ren.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231206/2063a36c/attachment.html>

From Joshua.D.Shaw at dartmouth.edu  Wed Dec  6 13:13:31 2023
From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw)
Date: Wed, 6 Dec 2023 18:13:31 +0000
Subject: [Archivesspace_Users_Group] how to
	add	a	new	locale	to	ArchivesSpace?
In-Reply-To: <AM9PR02MB6915C693049E3712B7F54CE48884A@AM9PR02MB6915.eurprd02.prod.outlook.com>
References: <AM9PR02MB6915A0EFA9E9233D27C3C0A48884A@AM9PR02MB6915.eurprd02.prod.outlook.com>
 <BL0PR03MB429285CBD09CD003B28C4F6AAB84A@BL0PR03MB4292.namprd03.prod.outlook.com>
 <AM9PR02MB6915C05D88CFCC135AC8CF138884A@AM9PR02MB6915.eurprd02.prod.outlook.com>
 <BL0PR03MB429277DEAE0184082B3D4974AB84A@BL0PR03MB4292.namprd03.prod.outlook.com>
 <AM9PR02MB6915C693049E3712B7F54CE48884A@AM9PR02MB6915.eurprd02.prod.outlook.com>
Message-ID: <BL0PR03MB42928B8DD87506A258957A24AB84A@BL0PR03MB4292.namprd03.prod.outlook.com>

One thing you might try is initializing the AppConfig[:locale] setting  in the plugin itself, since it may be an order of operations issue where the main config loads first which attempts to initialize an unknown language (because the plugin hasn't loaded yet).

jds


________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Ron Van den Branden <Ron.VandenBranden at antwerpen.be>
Sent: Wednesday, December 6, 2023 12:00 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

Hi Joshua,

Thanks again for your detailed steps! Although a first attempt didn't work (startup keeps choking on the original languages list), I'm sure we'll get there, with more time. Thanks for pointing me in the good direction: overriding the language list via plugin initialization. I'll definitely check out those other plugins for inspiration.

Best,

Ron


________________________________
Van: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> namens Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Verzonden: woensdag 6 december 2023 17:21
Aan: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Onderwerp: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

U ontvangt niet vaak e-mail van joshua.d.shaw at dartmouth.edu. Meer informatie over waarom dit belangrijk is<https://aka.ms/LearnAboutSenderIdentification>

WAARSCHUWING: DIT IS EEN EXTERNE MAIL

Deze mail komt van buiten onze organisatie. Kijk eerst of je het mailadres en de afzender herkent en/of vertrouwt. Doe dat voor je bijlagen opent of links aanklikt. Zo houden we onze organisatie veiliger voor phishing.

Hey Ron

Here's the way I'd do this.


  1.  Create a new directory in the plugin folder in your ArchivesSpace directory. Call it something like aspace_custom_locatizations (or whatever you want)
  2.  In that new directory, create two new directories: backend and frontend
  3.  In the backend directory, add a file called plugin_init.rb. Put the contents of the monkey patch in that file
  4.  In the frontend directory, add a file tree that mimics the locales directory in the core code:
     *   locales/
     *   locales/enums
  5.  Add your new dutch locales files to those two locations. Name them nl.yml
  6.  In your config file, add your plugin name (the directory name in step 1) to the list of plugins that are active: AppConfig[:plugins] is the key you want to edit.

Since I haven't tested this, there may be some gotchas I'm not thinking about as far as the monkeypatch and where the locales list may also be referenced, but this is the approach I'd take.

There's more info on that tech docs page and there are a bunch of examples to be found on the Awesome ArchivesSpace repo (https://github.com/archivesspace/awesome-archivesspace) and Hudson Molonglo's repos (https://github.com/hudmol) and https://gitlab.gaiaresources.com.au/explor<https://gitlab.gaiaresources.com.au/explore>

jds


________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Ron Van den Branden <Ron.VandenBranden at antwerpen.be>
Sent: Wednesday, December 6, 2023 11:01 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

Hi Joshua,

Ok, thanks for that pointer! The point is that we couldn't find that common/aspace_i18n.rb file in the ArchivesSpace distribution code. Or are you suggesting to add it in a plugin? If so, would you mind guiding me a bit more?

I don't think we've succeeded in building from source (I'm on Windows, so I'm probably at a loss for local testing, I recall some Ruby build incompatibilities).

Best,

Ron

________________________________
Van: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> namens Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Verzonden: woensdag 6 december 2023 16:44
Aan: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Onderwerp: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

U ontvangt niet vaak e-mail van joshua.d.shaw at dartmouth.edu. Meer informatie over waarom dit belangrijk is<https://aka.ms/LearnAboutSenderIdentification>

WAARSCHUWING: DIT IS EEN EXTERNE MAIL

Deze mail komt van buiten onze organisatie. Kijk eerst of je het mailadres en de afzender herkent en/of vertrouwt. Doe dat voor je bijlagen opent of links aanklikt. Zo houden we onze organisatie veiliger voor phishing.

Hey Ron

In addition to what Christine lists....

Off the top of my head (so take with a grain of salt since I haven't actually tested this!)...

In a plugin init (probably a backend plugin_init), monkey patch the self.supported_locales method in common/aspace_i18n.rb. Maybe something like

module I18n
def self.supported_locales
??????enhanced_locales = LOCALES

??????# map I18n language code => ArchivesSpace enumerations:language_iso639_2 code
??????# enumerations iso codes found in common/locales/enums
??????enhanced_locales['nl'] = 'dut'

??????enhanced_locales
end
end

Then you could add your new dutch locale file nl.yml within that same plugin.

OR

You could grab the code tree from github, patch it locally and build your patched application.

Both approaches have their own set of headaches as far as maintenance.

To contribute and other tech docs: https://archivesspace.github.io/tech-docs/readme_develop.html

Hope that helps!
Joshua



________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Ron Van den Branden <Ron.VandenBranden at antwerpen.be>
Sent: Wednesday, December 6, 2023 9:51 AM
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

Hi all,
We're in the process of customizing the ArchivesSpace (3.4.1) staff interface for use in a Dutch-speaking context. We would like to translate the back-end user interface to Dutch. So far, in order to gain speed, we've resorted to tweaking the en.yml localization files with Dutch labels. In the longer run, hijacking "English" for another language feels like a hack, though.
The documentation for "customizing text" at https://archivesspace.github.io/tech-docs/customization/locales.html  does mention where strings can be customized in current locales, but not how new locales can be added. Simply adding new locale files for new languages, with according names and language codes, at the right locations doesn't seem to do the trick:

  *   either the language is not being offered in the list of available languages
  *
when additionally the new language is specified explicitly in the config/config.rb file as AppConfig[:locale] = :nl , this yields following error at startup:

JSONModel::ValidationException: #<:ValidationException: {:errors=>{"defaults/locale"=>["Invalid value 'nl'.  Must be one of: en, fr, de, ja, es"]}}>

                      validate at uri:classloader:/jsonmodel_type.rb:385

            with_validator_for at uri:classloader:/validator_cache.rb:41

...so there must be more to adding a new locale. Yet, we can't find where in the ArchivesSpace distribution code such a list of default locales can be found or edited.
We did find the file in the ArchivesSpace source tree at https://github.com/archivesspace/archivesspace/blob/master/common/aspace_i18n.rb#L28 which defines above list of locales This file can't be found in the distribution code, however, so it's not clear how it relates to the distribution code. The commit history also shows commits from the Weblate project at https://hosted.weblate.org/projects/archivesspace-interfaces/#languages, which contains additional languages Portuguese and Italian.
This leads to following questions:

  *   what's the mechanism for adding a new locale to an ArchivesSpace instance?
  *   if our translations would reach a stage of being of broader interest, what would be the procedure for contributing them?

Kind regards,
Ron


Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis

Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving |  Boeken en Letteren

Minderbroedersstraat 22, 2000 Antwerpen

Grote Markt 1, 2000 Antwerpen

gsm +32 0485 02 80 50 | tel. +32 3 222 93 30

letterenhuis.be<http://www.letterenhuis.be/> | instagram<https://www.instagram.com/letterenhuis/> | facebook<https://www.facebook.com/Letterenhuis>



Proclaimer

Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, niet voor u bestemd is, vragen we u vriendelijk om dat te melden aan de afzender. Deze e-mail en de bijlagen zijn namelijk offici?le documenten van de stad Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie bevatten. Als stad nemen we privacy heel serieus en willen we als een goede huisvader waken over de vertrouwelijkheid van documenten. Als u dit bericht per vergissing hebt ontvangen of ergens hebt gevonden, wees dan zo eerlijk om het meteen te verwijderen en het niet verder te verspreiden of te kopi?ren.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231206/eb358b4e/attachment.html>

From bailey-grace.harrell at lyrasis.org  Wed Dec  6 13:27:29 2023
From: bailey-grace.harrell at lyrasis.org (Bailey-Grace Harrell)
Date: Wed, 6 Dec 2023 18:27:29 +0000
Subject: [Archivesspace_Users_Group] ArchivesSpace Virtual Member Forum 2024
 - Save the Date and Call for Planning Team Members
Message-ID: <CYYPR22MB4158E361DF3B7CD6254CEEAEC684A@CYYPR22MB4158.namprd22.prod.outlook.com>

ArchivesSpace Virtual Member Forum 2024 - Save the Date and Call for Planning Team Members

Mark your calendars for our 2024 Virtual Member Forum! Taking place March 26-27, 2024, our Virtual Member Forum will be a two-day event spanning a variety of time zones and ArchivesSpace experience levels.

If you are interested in serving on the planning team for this forum, please email Jessica Crouch at jessica.crouch at lyrasis.org<mailto:jessica.crouch at lyrasis.org> by December 8, 2023.  The Virtual Member Forum is one of our largest events of the year and we are looking for volunteers to review proposals, develop the schedule, and help make this forum great!

More information will be provided soon about how to propose a topic or presentation.  Registration will open closer to the event date.  For now, be sure to save the date on your calendar.  We look forward to ?seeing? many of you there.


Bailey-Grace Harrell
ArchivesSpace Program Assistant
Bailey-grace.harrell at lyrasis.com<mailto:Bailey-grace.harrell at lyrasis.com>

[signature_1444851839]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231206/b6a753bc/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 224996 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231206/b6a753bc/attachment-0001.png>

From shand at ap.org  Wed Dec  6 14:03:00 2023
From: shand at ap.org (Hand, Sarit)
Date: Wed, 6 Dec 2023 19:03:00 +0000
Subject: [Archivesspace_Users_Group]
 =?windows-1252?q?Digital_Objects_=96_?=
 =?windows-1252?q?examples_of_ASpace_records_+_repository_objects=3F?=
In-Reply-To: <BN9PR03MB59794FED90D7CD980F3465EEF085A@BN9PR03MB5979.namprd03.prod.outlook.com>
References: <BN9PR03MB59794A86E5FCB36879F0C5FDF085A@BN9PR03MB5979.namprd03.prod.outlook.com>
 <0bc9ca69-de9a-4006-bb1e-b786269e2036.5bc9e4a4-201a-4113-8500-06887445b2b4.06ee5d14-4db3-46b0-923e-d6ef5ea1d4d2@emailsignatures365.codetwo.com>
 <0bc9ca69-de9a-4006-bb1e-b786269e2036.1fe061b8-c04b-4022-ab6c-ea3cb89cd359.c1aefc88-c79b-4b8b-bccc-2415134842fa@emailsignatures365.codetwo.com>
 <BN0PR20MB3877616E8FD44117680B6E44D385A@BN0PR20MB3877.namprd20.prod.outlook.com>
 <IA1PR02MB94660DD0567B799F055770F4B585A@IA1PR02MB9466.namprd02.prod.outlook.com>
 <BN9PR03MB59794FED90D7CD980F3465EEF085A@BN9PR03MB5979.namprd03.prod.outlook.com>
Message-ID: <BL0PR16MB24197FCC920DA629EB82AF78CF84A@BL0PR16MB2419.namprd16.prod.outlook.com>

Hi Morgan,

I grapple with this issue every time I get new content and if it is born digital versus digitized. The overall determining factors include how you catalogue your collections in ASpace and the digital repository system you use; how they integrate. There may be limitations, or the complexity involved in generating all the records and links, and time and staffing to do the work that may inform your practices. How much can you automate or do in bulk? Consider too, how the DR handles files and related information packages, representations etc.

Another factor is deciding how you want to use the DO record. I know many people use it just as a carrier for the link to the object in the DR. I could argue skipping the DO altogether and using a notes sub-record and simply put the link in the AO record itself. But that, again, may be determined by the integration options between the two systems and workflows you can set up. Add that you will have to encode the link in the notes field each time (unless you can automate it).  Will you use ASpace for descriptive info and the DR for everything technical? Can the system automate migrating that data over if you want one true source for everything?

Due to the integration options for our systems, I depend upon the DR to manage the technical metadata and UIDs for anything digital, some of which, like the UID and links, are populated into ASpace records but not detailed techMD. I generally follow the practice that the DO represents the AO. If the lowest child record is a folder, then the DO linked, represents the digital folder, not the content. This means, in our system, the link in the DO record will go to the folder in the DR. That folder will contain the files/assets/digital items, even if it is 1 or 1 thousand files. I tried the idea of creating single DOs per file and linking many DOs to a single AO, but that gets complicated and there is no real new info in the DO to warrant filling up the database nor do we have the resources to describe every page in every folder but I have had to adjust our records to add levels of descriptions so I can link something. I have found this practice helps to resolve a lot of my ?what to do? questions. For example, we photograph our artifacts, nothing fancy, but we get several images, from different angles if the object warrants it. The images are saved in folders using the object?s ID (in-house number) to name the folder and each image gets a suffix (_01, _02,?). That folder of images is what the DO represents and the link in the DO will resolve to. I apply the same concept to digital files I have for meetings where I have digital recordings, video, audio, text and PDFs. Each meeting is represented by the AO and the DO will link to the folder containing the files (the folder intellectually represents the meeting). I may describe the contents of the folder, including file types in the extent or physical description; I happen to be working on this collection, now so am working out the details.

Honestly, I remind myself that as an archivist, my job is to describe to the best of my ability and make it accessible, which sometimes means, researchers will have to sift through and read individual files for themselves to determine what it is. If I provide individual links to individual items, researchers will be clicking forever just to scan a folder of items. I also do pilot tests to check usability. But all of this is determined by the system you are using, how content is presented in the PUI, and overall functionality.

Hope that helps.
Always happy to discuss.

Cheers,
[cid:image001.png at 01DA2843.4831BCF0]                                              [cid:image002.jpg at 01DA2843.4831BCF0]
Sarit Hand                                                       200 Liberty St.
Digital Archivist                                               New York, NY 10281
Corporate Archives                                         T 212.621.7035


shand at ap.org
www.ap.org<http://www.ap.org/>
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of McKeehan, Morgan
Sent: Tuesday, December 5, 2023 5:18 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Digital Objects ? examples of ASpace records + repository objects?


[EXTERNAL]
Thank you for all the responses to this question! It's a huge help seeing the range of examples y'all have provided.

I will reach out to folks individually with followup questions. Just wanted to send a big thanks for all the time and thought folks put into sharing examples. We really appreciate it!

Morgan

------------------------
Morgan McKeehan (she/her/hers)
Digital Collections Specialist
University Libraries
The University of North Carolina at Chapel Hill
morganem at email.unc.edu<mailto:morganem at email.unc.edu>
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Clair, Kevin <kmc35 at psu.edu<mailto:kmc35 at psu.edu>>
Sent: Tuesday, December 5, 2023 15:05
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Digital Objects ? examples of ASpace records + repository objects?

You don't often get email from kmc35 at psu.edu<mailto:kmc35 at psu.edu>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
It's my favorite ArchivesSpace question!

I've managed this a couple of different ways. When I worked at the University of Denver we had (well, presumably they still have) a home-grown digital asset management system that relied entirely on ArchivesSpace as the metadata system of record. For that we assumed that every object in the digital repository also had a metadata record in ArchivesSpace, and we used the update-feed API endpoint to communicate when new digital objects had been created or existing ones had been updated so that the repository would reindex. I'm sure somewhere I still have my documentation of how that data model worked and can forward it to you if it's of interest, with the caveat that I left DU four years ago and I don't know how much it has changed in the meantime.

Here at Penn State, our digital object guidelines state that every item in our repository should have a unique identifier, which for bibliographic materials is its OCLC number and for archival materials is based on the ArchivesSpace reference ID. We've found, as Sarah described, that this poses problems with older digital collections that were published before we had guidelines, where their source collections are processed at the folder level but the digital collection is published at the item level. How we handle that varies based on the collection. Sometimes we will re-publish the digital collection to reflect the arrangement of the archival collection; more rarely, we will maintain the digital collection as it is and re-arrange the archival collection to reflect CONTENTdm. Ideally we want to be at the point where we have a strict 1:1 relationship between archival object and DAO records in ArchivesSpace. (Technically 1:2, because we manage access and preservation digital objects separately.)

We considered and abandoned the One Item, Many DAOs approach Sarah describes, although if you know where to look in our PUI you can definitely still find some examples of it...

Happy to talk more about this and/or share documentation, although I feel like our documentation is probably inadequate (isn't it always, though?).

cheers
-kevin

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Newhouse, Sarah <snewhouse at sciencehistory.org<mailto:snewhouse at sciencehistory.org>>
Sent: Tuesday, December 5, 2023 1:09 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Digital Objects ? examples of ASpace records + repository objects?

Morgan,

We've been putting off a similar discussion for a while now, because of all the reasons you've already outlined.

We initially tried using the DAO component for access, to link our ASpace PUI with our digital collections, but ran into issues with differing levels of description between the PUI and our DC. Specifically, a few large collections that had grant-funded digitization to scan and create item-level records in the DC for everything. So a folder or volume/item-level component in ASpace would have 100+ DAOs linked to it, which made for a really unhelpful PUI experience for users looking at that component with just an endless vertical scroll of DAOs.

Our longer-term solution is to look not at ASpace, but at the data in our DC and see if there's a way we can create or simulate folder or volume-level works for relevant items in the DC and link to those using the ASpace DAOs, so there's one DAO for one ASpace component (folder, volume, box, what have you). Luckily, when the DC was built (before ASpace adoption) the developers built in a field for physical location that records box, folder, and volume info (scroll down, under "Institutional location"): https://digital.sciencehistory.org/works/k0lxixk

Our interim solution is to use the Existence and Location of Copies note and link to collection-level works in our DC. Example here: https://archives.sciencehistory.org/repositories/3/resources/635

Happy to talk more over Zoom or email if more details would be helpful! We're a small library just trying to make access as easy as possible with the tools we've got.


Science History Institute
Chemistry ? Engineering ? Life Sciences
315 Chestnut Street ? Philadelphia, PA 19106 ? U.S.A.
We tell the stories behind the science.
sciencehistory.org<https://www.sciencehistory.org/>
__________________________________

Sarah Newhouse   (she, her, hers)
Digital Preservation Archivist
Othmer Library of Chemical History
t. +1.215.873.8249
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of McKeehan, Morgan <morganem at live.unc.edu<mailto:morganem at live.unc.edu>>
Sent: Tuesday, December 5, 2023 10:42 AM
To: archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org> <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Digital Objects ? examples of ASpace records + repository objects?

Hi everyone,

I?m looking for examples of how other institutions have handled relationships between ASpace records and digital repository content, in cases when the physical arrangement vs. intellectual arrangement poses object-modeling challenges for digitized representations.

For example, in your systems do you have scenarios when an ASpace archival object record may have many ASpace digital object (DO) records linked to it, with each DO record corresponding to an individual object in your digital repository system? Conversely, perhaps there are also  situations where a single digital repository object contains files/digitized pages that are described by separate archival object records ? ie, a folder of stuff that was digitized as one grouping, but actually corresponds to more than one individual descriptive component?

At my institution, we?re working through these issues as we?re migrating our digitized materials to a new digital repository system at the same time as we?re also migrating our finding aids/archival data to ASpace. We would welcome any examples that others can share, in case you may have approaches from what has worked well, or lessons learned about what to avoid.

Please also feel free to message me off-list if more context or clarification about what I?m asking would be helpful. I?m happy to discuss more about our workflows and object modeling plans so far.

I?d also be happy to set up a zoom call if anyone has examples to share that it would be easier to walk through via zoom. I totally understand there may be examples that just seem too complicated to try to explain in an email!

Here's a little more explanation about the kinds of linking situations I?m asking about:

In our new digital repository, we plan to model digitized materials as repository objects based on the physical containers. For example, all digitized pages from a folder of correspondence would equal 1 repository object (a ?Work?). The URL of the repository object will provide the File Version value for an ASpace Digital Object record, and that DO record will be linked to the relevant archival object record that contains the description for the original materials.

In cases such as a grouping of documents that is housed in a range of physical folders, this will mean many DO records linked to an archival object record. A common scenario is something like: a descriptive component with Title: ?Correspondence, 1800?, housed in ?Folders 65-75?. This arrangement will give us 11 DO records linked to the ?Correspondence, 1800? archival object record. In many cases, folder ranges will be even larger, so there could easily be 20-30 or more DO records linked to an AO record. However, if we instead modeled all scans from Folders 65-75 as 1 object in our digital repository, since each folder contains 100+ pages, that arrangement would be a large and cumbersome repository object for users to navigate. Neither option seems great. We?re interested in learning about how others handle these types of situations!

Thanks for any examples or insights you can share,

Morgan

------------------------
Morgan McKeehan (she/her/hers)
Digital Collections Specialist
University Libraries
The University of North Carolina at Chapel Hill
morganem at email.unc.edu<mailto:morganem at email.unc.edu>
The information contained in this communication is intended for the use of the designated recipients named above. If the reader of this communication is not the intended recipient, you are hereby notified that you have received this communication in error, and that any review, dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify The Associated Press immediately by telephone at +1-212-621-1500 and delete this email. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231206/af15d7b9/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 5729 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231206/af15d7b9/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 1715 bytes
Desc: image002.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231206/af15d7b9/attachment.jpg>

From shand at ap.org  Wed Dec  6 14:05:51 2023
From: shand at ap.org (Hand, Sarit)
Date: Wed, 6 Dec 2023 19:05:51 +0000
Subject: [Archivesspace_Users_Group] Export resource records to Excel
In-Reply-To: <SJ0PR06MB744011C2DC5995B982353247AC84A@SJ0PR06MB7440.namprd06.prod.outlook.com>
References: <SJ0PR06MB744011C2DC5995B982353247AC84A@SJ0PR06MB7440.namprd06.prod.outlook.com>
Message-ID: <BL0PR16MB2419B39C699F5EC8EAC271C2CF84A@BL0PR16MB2419.namprd16.prod.outlook.com>

Have you tried the bulk updater plug-in? I honestly don't recall if its been added to the core code yet. But that will allow you to download a spreadsheet of a single resource. However, there are some sub-records you will not get in that. That's a development issue. Wendy Scheir from New School is behind that plug-in!

Cheers,
[cid:image001.png at 01DA284D.509C14D0]                                              [cid:image002.jpg at 01DA284D.509C14D0]
Sarit Hand                                                       200 Liberty St.
Digital Archivist                                               New York, NY 10281
Corporate Archives                                         T 212.621.7035


shand at ap.org
www.ap.org<http://www.ap.org/>
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Nick Richbell
Sent: Wednesday, December 6, 2023 10:45 AM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Export resource records to Excel

You don't often get email from nrichbe at clemson.edu<mailto:nrichbe at clemson.edu>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>

[EXTERNAL]
Good morning, List:

I am new to ArchivesSpace and am slowly figuring this out. One thing I need some help with is whether I can export a resource (all of the collection) to Excel? I've tried to find a solution but have had no success.

Any advice will be gratefully received!

Thanks, Nick





Nick Richbell, MLIS

Head, Special Collections and Archives

Clemson University Libraries

Clemson University



Strom Thurmond Institute

230 Kappa Street

Clemson, SC  29634

864-656-3875

http://libraries.clemson.edu/specialcollections/



 [cid:image003.png at 01DA284D.509C14D0]

The information contained in this communication is intended for the use of the designated recipients named above. If the reader of this communication is not the intended recipient, you are hereby notified that you have received this communication in error, and that any review, dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify The Associated Press immediately by telephone at +1-212-621-1500 and delete this email. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231206/2430168f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 5729 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231206/2430168f/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 1715 bytes
Desc: image002.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231206/2430168f/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 3417 bytes
Desc: image003.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231206/2430168f/attachment-0001.png>

From Joshua.D.Shaw at dartmouth.edu  Wed Dec  6 16:03:41 2023
From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw)
Date: Wed, 6 Dec 2023 21:03:41 +0000
Subject: [Archivesspace_Users_Group] how
	to	add	a	new	locale	to	ArchivesSpace?
In-Reply-To: <BL0PR03MB42928B8DD87506A258957A24AB84A@BL0PR03MB4292.namprd03.prod.outlook.com>
References: <AM9PR02MB6915A0EFA9E9233D27C3C0A48884A@AM9PR02MB6915.eurprd02.prod.outlook.com>
 <BL0PR03MB429285CBD09CD003B28C4F6AAB84A@BL0PR03MB4292.namprd03.prod.outlook.com>
 <AM9PR02MB6915C05D88CFCC135AC8CF138884A@AM9PR02MB6915.eurprd02.prod.outlook.com>
 <BL0PR03MB429277DEAE0184082B3D4974AB84A@BL0PR03MB4292.namprd03.prod.outlook.com>
 <AM9PR02MB6915C693049E3712B7F54CE48884A@AM9PR02MB6915.eurprd02.prod.outlook.com>
 <BL0PR03MB42928B8DD87506A258957A24AB84A@BL0PR03MB4292.namprd03.prod.outlook.com>
Message-ID: <BL0PR03MB42924E671F6C97F4EA8ADFF6AB84A@BL0PR03MB4292.namprd03.prod.outlook.com>

The other way to do this (a bit hacky) is to expand the common.jar file in /lib, make your edits to the relevant I18n file (common/aspace_i18n.rb), and then recompress the jar file.

This works for any edits you need to core, but its hacky because its not really a sustainable way to do things since you need to edit the same file for every? update to the core code.

jds


________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Sent: Wednesday, December 6, 2023 1:13 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

One thing you might try is initializing the AppConfig[:locale] setting  in the plugin itself, since it may be an order of operations issue where the main config loads first which attempts to initialize an unknown language (because the plugin hasn't loaded yet).

jds


________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Ron Van den Branden <Ron.VandenBranden at antwerpen.be>
Sent: Wednesday, December 6, 2023 12:00 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

Hi Joshua,

Thanks again for your detailed steps! Although a first attempt didn't work (startup keeps choking on the original languages list), I'm sure we'll get there, with more time. Thanks for pointing me in the good direction: overriding the language list via plugin initialization. I'll definitely check out those other plugins for inspiration.

Best,

Ron


________________________________
Van: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> namens Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Verzonden: woensdag 6 december 2023 17:21
Aan: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Onderwerp: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

U ontvangt niet vaak e-mail van joshua.d.shaw at dartmouth.edu. Meer informatie over waarom dit belangrijk is<https://aka.ms/LearnAboutSenderIdentification>

WAARSCHUWING: DIT IS EEN EXTERNE MAIL

Deze mail komt van buiten onze organisatie. Kijk eerst of je het mailadres en de afzender herkent en/of vertrouwt. Doe dat voor je bijlagen opent of links aanklikt. Zo houden we onze organisatie veiliger voor phishing.

Hey Ron

Here's the way I'd do this.


  1.  Create a new directory in the plugin folder in your ArchivesSpace directory. Call it something like aspace_custom_locatizations (or whatever you want)
  2.  In that new directory, create two new directories: backend and frontend
  3.  In the backend directory, add a file called plugin_init.rb. Put the contents of the monkey patch in that file
  4.  In the frontend directory, add a file tree that mimics the locales directory in the core code:
     *   locales/
     *   locales/enums
  5.  Add your new dutch locales files to those two locations. Name them nl.yml
  6.  In your config file, add your plugin name (the directory name in step 1) to the list of plugins that are active: AppConfig[:plugins] is the key you want to edit.

Since I haven't tested this, there may be some gotchas I'm not thinking about as far as the monkeypatch and where the locales list may also be referenced, but this is the approach I'd take.

There's more info on that tech docs page and there are a bunch of examples to be found on the Awesome ArchivesSpace repo (https://github.com/archivesspace/awesome-archivesspace) and Hudson Molonglo's repos (https://github.com/hudmol) and https://gitlab.gaiaresources.com.au/explor<https://gitlab.gaiaresources.com.au/explore>

jds


________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Ron Van den Branden <Ron.VandenBranden at antwerpen.be>
Sent: Wednesday, December 6, 2023 11:01 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

Hi Joshua,

Ok, thanks for that pointer! The point is that we couldn't find that common/aspace_i18n.rb file in the ArchivesSpace distribution code. Or are you suggesting to add it in a plugin? If so, would you mind guiding me a bit more?

I don't think we've succeeded in building from source (I'm on Windows, so I'm probably at a loss for local testing, I recall some Ruby build incompatibilities).

Best,

Ron

________________________________
Van: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> namens Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Verzonden: woensdag 6 december 2023 16:44
Aan: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Onderwerp: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

U ontvangt niet vaak e-mail van joshua.d.shaw at dartmouth.edu. Meer informatie over waarom dit belangrijk is<https://aka.ms/LearnAboutSenderIdentification>

WAARSCHUWING: DIT IS EEN EXTERNE MAIL

Deze mail komt van buiten onze organisatie. Kijk eerst of je het mailadres en de afzender herkent en/of vertrouwt. Doe dat voor je bijlagen opent of links aanklikt. Zo houden we onze organisatie veiliger voor phishing.

Hey Ron

In addition to what Christine lists....

Off the top of my head (so take with a grain of salt since I haven't actually tested this!)...

In a plugin init (probably a backend plugin_init), monkey patch the self.supported_locales method in common/aspace_i18n.rb. Maybe something like

module I18n
def self.supported_locales
??????enhanced_locales = LOCALES

??????# map I18n language code => ArchivesSpace enumerations:language_iso639_2 code
??????# enumerations iso codes found in common/locales/enums
??????enhanced_locales['nl'] = 'dut'

??????enhanced_locales
end
end

Then you could add your new dutch locale file nl.yml within that same plugin.

OR

You could grab the code tree from github, patch it locally and build your patched application.

Both approaches have their own set of headaches as far as maintenance.

To contribute and other tech docs: https://archivesspace.github.io/tech-docs/readme_develop.html

Hope that helps!
Joshua



________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Ron Van den Branden <Ron.VandenBranden at antwerpen.be>
Sent: Wednesday, December 6, 2023 9:51 AM
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

Hi all,
We're in the process of customizing the ArchivesSpace (3.4.1) staff interface for use in a Dutch-speaking context. We would like to translate the back-end user interface to Dutch. So far, in order to gain speed, we've resorted to tweaking the en.yml localization files with Dutch labels. In the longer run, hijacking "English" for another language feels like a hack, though.
The documentation for "customizing text" at https://archivesspace.github.io/tech-docs/customization/locales.html  does mention where strings can be customized in current locales, but not how new locales can be added. Simply adding new locale files for new languages, with according names and language codes, at the right locations doesn't seem to do the trick:

  *   either the language is not being offered in the list of available languages
  *
when additionally the new language is specified explicitly in the config/config.rb file as AppConfig[:locale] = :nl , this yields following error at startup:

JSONModel::ValidationException: #<:ValidationException: {:errors=>{"defaults/locale"=>["Invalid value 'nl'.  Must be one of: en, fr, de, ja, es"]}}>

                      validate at uri:classloader:/jsonmodel_type.rb:385

            with_validator_for at uri:classloader:/validator_cache.rb:41

...so there must be more to adding a new locale. Yet, we can't find where in the ArchivesSpace distribution code such a list of default locales can be found or edited.
We did find the file in the ArchivesSpace source tree at https://github.com/archivesspace/archivesspace/blob/master/common/aspace_i18n.rb#L28 which defines above list of locales This file can't be found in the distribution code, however, so it's not clear how it relates to the distribution code. The commit history also shows commits from the Weblate project at https://hosted.weblate.org/projects/archivesspace-interfaces/#languages, which contains additional languages Portuguese and Italian.
This leads to following questions:

  *   what's the mechanism for adding a new locale to an ArchivesSpace instance?
  *   if our translations would reach a stage of being of broader interest, what would be the procedure for contributing them?

Kind regards,
Ron


Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis

Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving |  Boeken en Letteren

Minderbroedersstraat 22, 2000 Antwerpen

Grote Markt 1, 2000 Antwerpen

gsm +32 0485 02 80 50 | tel. +32 3 222 93 30

letterenhuis.be<http://www.letterenhuis.be/> | instagram<https://www.instagram.com/letterenhuis/> | facebook<https://www.facebook.com/Letterenhuis>



Proclaimer

Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, niet voor u bestemd is, vragen we u vriendelijk om dat te melden aan de afzender. Deze e-mail en de bijlagen zijn namelijk offici?le documenten van de stad Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie bevatten. Als stad nemen we privacy heel serieus en willen we als een goede huisvader waken over de vertrouwelijkheid van documenten. Als u dit bericht per vergissing hebt ontvangen of ergens hebt gevonden, wees dan zo eerlijk om het meteen te verwijderen en het niet verder te verspreiden of te kopi?ren.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231206/9680f230/attachment.html>

From cnorton9 at library.rochester.edu  Wed Dec  6 16:04:21 2023
From: cnorton9 at library.rochester.edu (Norton, Channing)
Date: Wed, 6 Dec 2023 21:04:21 +0000
Subject: [Archivesspace_Users_Group] [EXT] Re: Export resource records
 to Excel
In-Reply-To: <BL0PR16MB2419B39C699F5EC8EAC271C2CF84A@BL0PR16MB2419.namprd16.prod.outlook.com>
References: <SJ0PR06MB744011C2DC5995B982353247AC84A@SJ0PR06MB7440.namprd06.prod.outlook.com>
 <BL0PR16MB2419B39C699F5EC8EAC271C2CF84A@BL0PR16MB2419.namprd16.prod.outlook.com>
Message-ID: <PH0PR07MB843195A31016C566238A6B8BCE84A@PH0PR07MB8431.namprd07.prod.outlook.com>

Sarit, Nick,

The bulk updater has been added to the core code. I don't recall the exact patch, perhaps 3.2. For the subrecords issue, I'm actually working on a new utility right now that will be able to help with that in a few weeks. Once I have something capable of doing these exports, I'll build out the documentation and put it all under a release tag in the following repo where I'm working.

https://github.com/C-Norton/Archivesspace_Collections_Manager


Channing Norton (He/Him/They/Them)
Senior Programmer Analyst
Digital Initiatives
University of Rochester

On Campus Tues, Wed

From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Hand, Sarit
Sent: Wednesday, December 6, 2023 2:06 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [EXT] Re: [Archivesspace_Users_Group] Export resource records to Excel

Have you tried the bulk updater plug-in? I honestly don't recall if its been added to the core code yet. But that will allow you to download a spreadsheet of a single resource. However, there are some sub-records you will not get in that. That's a development issue. Wendy Scheir from New School is behind that plug-in!

Cheers,
[cid:image001.png at 01DA285C.93C75F30]                                              [cid:image002.jpg at 01DA285C.93C75F30]
Sarit Hand                                                       200 Liberty St.
Digital Archivist                                               New York, NY 10281
Corporate Archives                                         T 212.621.7035


shand at ap.org<mailto:shand at ap.org>
www.ap.org<https://urldefense.com/v3/__http:/www.ap.org/__;!!CGUSO5OYRnA7CQ!acRB8y49X820mRDUJu_MgViQ4TFl2DytPoKNyCKKyhBNBT49Ds9Urrf-24o4UL95sdcU_WeeW3XdT5CwU6aoAw$>
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> On Behalf Of Nick Richbell
Sent: Wednesday, December 6, 2023 10:45 AM
To: archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Export resource records to Excel

You don't often get email from nrichbe at clemson.edu<mailto:nrichbe at clemson.edu>. Learn why this is important<https://urldefense.com/v3/__https:/aka.ms/LearnAboutSenderIdentification__;!!CGUSO5OYRnA7CQ!acRB8y49X820mRDUJu_MgViQ4TFl2DytPoKNyCKKyhBNBT49Ds9Urrf-24o4UL95sdcU_WeeW3XdT5DJNmZWZA$>

[EXTERNAL]
Good morning, List:

I am new to ArchivesSpace and am slowly figuring this out. One thing I need some help with is whether I can export a resource (all of the collection) to Excel? I've tried to find a solution but have had no success.

Any advice will be gratefully received!

Thanks, Nick





Nick Richbell, MLIS

Head, Special Collections and Archives

Clemson University Libraries

Clemson University



Strom Thurmond Institute

230 Kappa Street

Clemson, SC  29634

864-656-3875

http://libraries.clemson.edu/specialcollections/<https://urldefense.com/v3/__http:/libraries.clemson.edu/specialcollections/__;!!CGUSO5OYRnA7CQ!acRB8y49X820mRDUJu_MgViQ4TFl2DytPoKNyCKKyhBNBT49Ds9Urrf-24o4UL95sdcU_WeeW3XdT5AiuvvFSA$>



 [cid:image003.png at 01DA285C.93C75F30]
The information contained in this communication is intended for the use of the designated recipients named above. If the reader of this communication is not the intended recipient, you are hereby notified that you have received this communication in error, and that any review, dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify The Associated Press immediately by telephone at +1-212-621-1500 and delete this email. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231206/cec09597/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 5729 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231206/cec09597/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 1715 bytes
Desc: image002.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231206/cec09597/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 3417 bytes
Desc: image003.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231206/cec09597/attachment-0001.png>

From christine.dibella at lyrasis.org  Wed Dec  6 19:33:33 2023
From: christine.dibella at lyrasis.org (Christine Di Bella)
Date: Thu, 7 Dec 2023 00:33:33 +0000
Subject: [Archivesspace_Users_Group] [EXT] Re: Export resource records
 to Excel
In-Reply-To: <PH0PR07MB843195A31016C566238A6B8BCE84A@PH0PR07MB8431.namprd07.prod.outlook.com>
References: <SJ0PR06MB744011C2DC5995B982353247AC84A@SJ0PR06MB7440.namprd06.prod.outlook.com>
 <BL0PR16MB2419B39C699F5EC8EAC271C2CF84A@BL0PR16MB2419.namprd16.prod.outlook.com>
 <PH0PR07MB843195A31016C566238A6B8BCE84A@PH0PR07MB8431.namprd07.prod.outlook.com>
Message-ID: <MN2PR22MB1887A615938D50D1C28B6EEBF18BA@MN2PR22MB1887.namprd22.prod.outlook.com>

Thanks for sharing a link with a sneak preview of the data utility you're building, Channing. This sounds like a really useful project and it'll be great to hear more when you're ready.

(Just to limit confusion for people reading this thread, I should point out that the bulk updater plugin is not part of the core code of ArchivesSpace - it is a separate plugin developed by Hudson Molonglo for The New School and shared with the ArchivesSpace community. The ArchivesSpace team is working on plans to incorporate this functionality into an upcoming release of ArchivesSpace.)

Christine

Christine Di Bella
ArchivesSpace Senior Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>

[cid:image004.jpg at 01DA287B.1142A640]



From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Norton, Channing
Sent: Wednesday, December 6, 2023 4:04 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] [EXT] Re: Export resource records to Excel

Sarit, Nick,

The bulk updater has been added to the core code. I don't recall the exact patch, perhaps 3.2. For the subrecords issue, I'm actually working on a new utility right now that will be able to help with that in a few weeks. Once I have something capable of doing these exports, I'll build out the documentation and put it all under a release tag in the following repo where I'm working.

https://github.com/C-Norton/Archivesspace_Collections_Manager


Channing Norton (He/Him/They/Them)
Senior Programmer Analyst
Digital Initiatives
University of Rochester

On Campus Tues, Wed

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> On Behalf Of Hand, Sarit
Sent: Wednesday, December 6, 2023 2:06 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: [EXT] Re: [Archivesspace_Users_Group] Export resource records to Excel

Have you tried the bulk updater plug-in? I honestly don't recall if its been added to the core code yet. But that will allow you to download a spreadsheet of a single resource. However, there are some sub-records you will not get in that. That's a development issue. Wendy Scheir from New School is behind that plug-in!

Cheers,
[cid:image001.png at 01DA287A.9EBBA630]                                              [cid:image002.jpg at 01DA287A.9EBBA630]
Sarit Hand                                                       200 Liberty St.
Digital Archivist                                               New York, NY 10281
Corporate Archives                                         T 212.621.7035


shand at ap.org<mailto:shand at ap.org>
www.ap.org<https://urldefense.com/v3/__http:/www.ap.org/__;!!CGUSO5OYRnA7CQ!acRB8y49X820mRDUJu_MgViQ4TFl2DytPoKNyCKKyhBNBT49Ds9Urrf-24o4UL95sdcU_WeeW3XdT5CwU6aoAw$>
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> On Behalf Of Nick Richbell
Sent: Wednesday, December 6, 2023 10:45 AM
To: archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Export resource records to Excel

You don't often get email from nrichbe at clemson.edu<mailto:nrichbe at clemson.edu>. Learn why this is important<https://urldefense.com/v3/__https:/aka.ms/LearnAboutSenderIdentification__;!!CGUSO5OYRnA7CQ!acRB8y49X820mRDUJu_MgViQ4TFl2DytPoKNyCKKyhBNBT49Ds9Urrf-24o4UL95sdcU_WeeW3XdT5DJNmZWZA$>

[EXTERNAL]
Good morning, List:

I am new to ArchivesSpace and am slowly figuring this out. One thing I need some help with is whether I can export a resource (all of the collection) to Excel? I've tried to find a solution but have had no success.

Any advice will be gratefully received!

Thanks, Nick





Nick Richbell, MLIS

Head, Special Collections and Archives

Clemson University Libraries

Clemson University



Strom Thurmond Institute

230 Kappa Street

Clemson, SC  29634

864-656-3875

http://libraries.clemson.edu/specialcollections/<https://urldefense.com/v3/__http:/libraries.clemson.edu/specialcollections/__;!!CGUSO5OYRnA7CQ!acRB8y49X820mRDUJu_MgViQ4TFl2DytPoKNyCKKyhBNBT49Ds9Urrf-24o4UL95sdcU_WeeW3XdT5AiuvvFSA$>



 [cid:image003.png at 01DA287A.9EBBA630]
The information contained in this communication is intended for the use of the designated recipients named above. If the reader of this communication is not the intended recipient, you are hereby notified that you have received this communication in error, and that any review, dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify The Associated Press immediately by telephone at +1-212-621-1500 and delete this email. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231207/88ef266a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 5729 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231207/88ef266a/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 1715 bytes
Desc: image002.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231207/88ef266a/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 3417 bytes
Desc: image003.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231207/88ef266a/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.jpg
Type: image/jpeg
Size: 56099 bytes
Desc: image004.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231207/88ef266a/attachment-0001.jpg>

From christine.dibella at lyrasis.org  Wed Dec  6 19:39:46 2023
From: christine.dibella at lyrasis.org (Christine Di Bella)
Date: Thu, 7 Dec 2023 00:39:46 +0000
Subject: [Archivesspace_Users_Group] how to add a
	new	locale	to	ArchivesSpace?
In-Reply-To: <AM9PR02MB691594E9CDA01556BCDC09F88884A@AM9PR02MB6915.eurprd02.prod.outlook.com>
References: <AM9PR02MB6915A0EFA9E9233D27C3C0A48884A@AM9PR02MB6915.eurprd02.prod.outlook.com>
 <MN2PR22MB1887D0E3CF6329D21613A5F9F184A@MN2PR22MB1887.namprd22.prod.outlook.com>
 <AM9PR02MB691594E9CDA01556BCDC09F88884A@AM9PR02MB6915.eurprd02.prod.outlook.com>
Message-ID: <MN2PR22MB1887BB4BA1E7B77AFEBCB96CF18BA@MN2PR22MB1887.namprd22.prod.outlook.com>

Hi Ron,

It sounds like Joshua has given you good guidance for making translations work in your local deployment in the interim, but if you get to the point where you're ready to share the in-progress translation with an eye toward it going into the core code eventually, please let me know. There's the pull request option I mentioned before, but we also use a service called Weblate<https://hosted.weblate.org/projects/archivesspace-interfaces/> where translations can be worked on in a crowdsourced way. We'd love to get a Dutch set started on it.

Christine

From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Ron Van den Branden
Sent: Wednesday, December 6, 2023 10:57 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

Hi Christine,

Many thanks for your detailed answer, and the complete overview of where to look for localization files.

Editing the yml files (at least those under common and frontend) is exactly the approach we've taken. So far, with the "hack" of editing the translations in the en.yml files.

I appreciate including a new translation into the ArchivesSpace code would take some time and thourough review. What I'm missing, still, is an answer to the question whether it's possible in the meantime to "properly" add a new localization, and register those nl.yml files as a NL localization in an ArchivesSpace distribution. That would make it easier, IMO, to share and contribute those Dutch translation files in an earlier stage with potential interested parties, and offer them in a more mature stage for inclusion into ArchivesSpace.

Best,

Ron

________________________________
Van: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> namens Christine Di Bella <christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>>
Verzonden: woensdag 6 december 2023 16:42
Aan: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Onderwerp: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?


WAARSCHUWING: DIT IS EEN EXTERNE MAIL

Deze mail komt van buiten onze organisatie. Kijk eerst of je het mailadres en de afzender herkent en/of vertrouwt. Doe dat voor je bijlagen opent of links aanklikt. Zo houden we onze organisatie veiliger voor phishing.

Hello Ron,



It's great to hear that you're working on customizing your interfaces to have the option of providing labels in Dutch. I believe there are some institutions in the Netherlands, Belgium, and Luxembourg that have already done that, and you may hear from them here or directly. That would likely give you a very significant head start on your customization.



The Dutch translations themselves have not been contributed to the core ArchivesSpace yet, but we would be very interested in having them. We have a few options for contributing translations to ArchivesSpace, including using the Weblate service. If you are comfortable working directly with the .yml files, however, you need to first grab the ones from our GitHub repository itself. If you only use the ones in a release distribution file, your interface will be only partially translated.



These are the six directories to look for:

https://github.com/archivesspace/archivesspace/tree/master/common/locales

https://github.com/archivesspace/archivesspace/tree/master/common/locales/enums

https://github.com/archivesspace/archivesspace/tree/master/frontend/config/locales

https://github.com/archivesspace/archivesspace/tree/master/frontend/config/locales/help

https://github.com/archivesspace/archivesspace/tree/master/public/config/locales



https://github.com/archivesspace/archivesspace/tree/master/reports (there are locale files for each of the reports in the subdirectories under this main directory)



It's probably easiest to use the en.yml ones as your starting point since the labels in the file (the text that appears before the colons) need to stay in English. Follow the pattern you see and make a set where each file is named nl.yml. Within the files, change the text that appears after the colon for each entry you want to be in Dutch. (Don't change any of the formatting or line spacing since a computer is very literal.)



Once you've made all the changes you want, you can pull request the new files to us via GitHub, we can review, and then when all is correct and working like it should we will include them in a future release of ArchivesSpace.



There's plenty more to say, but I'll start there and see if anyone who's currently working with a translated interface or with translations has advice to offer. We're always interested in people submitting more languages for the ArchivesSpace application or improving the ones we have.



Christine



Christine Di Bella

ArchivesSpace Senior Program Manager

christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>



[cid:image001.jpg at 01DA287B.F75CBF30]







From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> On Behalf Of Ron Van den Branden
Sent: Wednesday, December 6, 2023 9:51 AM
To: archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?



Hi all,

We're in the process of customizing the ArchivesSpace (3.4.1) staff interface for use in a Dutch-speaking context. We would like to translate the back-end user interface to Dutch. So far, in order to gain speed, we've resorted to tweaking the en.yml localization files with Dutch labels. In the longer run, hijacking "English" for another language feels like a hack, though.

The documentation for "customizing text" at https://archivesspace.github.io/tech-docs/customization/locales.html  does mention where strings can be customized in current locales, but not how new locales can be added. Simply adding new locale files for new languages, with according names and language codes, at the right locations doesn't seem to do the trick:

  *   either the language is not being offered in the list of available languages
  *   when additionally the new language is specified explicitly in the config/config.rb file as AppConfig[:locale] = :nl , this yields following error at startup:

JSONModel::ValidationException: #<:ValidationException: {:errors=>{"defaults/locale"=>["Invalid value 'nl'.  Must be one of: en, fr, de, ja, es"]}}>

                      validate at uri:classloader:/jsonmodel_type.rb:385

            with_validator_for at uri:classloader:/validator_cache.rb:41

...so there must be more to adding a new locale. Yet, we can't find where in the ArchivesSpace distribution code such a list of default locales can be found or edited.

We did find the file in the ArchivesSpace source tree at https://github.com/archivesspace/archivesspace/blob/master/common/aspace_i18n.rb#L28 which defines above list of locales This file can't be found in the distribution code, however, so it's not clear how it relates to the distribution code. The commit history also shows commits from the Weblate project at https://hosted.weblate.org/projects/archivesspace-interfaces/#languages, which contains additional languages Portuguese and Italian.

This leads to following questions:

  *   what's the mechanism for adding a new locale to an ArchivesSpace instance?
  *   if our translations would reach a stage of being of broader interest, what would be the procedure for contributing them?

Kind regards,

Ron



Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis

Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving |  Boeken en Letteren

Minderbroedersstraat 22, 2000 Antwerpen

Grote Markt 1, 2000 Antwerpen

gsm +32 0485 02 80 50 | tel. +32 3 222 93 30

letterenhuis.be<http://www.letterenhuis.be/> | instagram<https://www.instagram.com/letterenhuis/> | facebook<https://www.facebook.com/Letterenhuis>



Proclaimer

Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, niet voor u bestemd is, vragen we u vriendelijk om dat te melden aan de afzender. Deze e-mail en de bijlagen zijn namelijk offici?le documenten van de stad Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie bevatten. Als stad nemen we privacy heel serieus en willen we als een goede huisvader waken over de vertrouwelijkheid van documenten. Als u dit bericht per vergissing hebt ontvangen of ergens hebt gevonden, wees dan zo eerlijk om het meteen te verwijderen en het niet verder te verspreiden of te kopi?ren.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231207/90c0d8d5/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 56099 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231207/90c0d8d5/attachment.jpg>

From christine.dibella at lyrasis.org  Wed Dec  6 20:02:17 2023
From: christine.dibella at lyrasis.org (Christine Di Bella)
Date: Thu, 7 Dec 2023 01:02:17 +0000
Subject: [Archivesspace_Users_Group] Digital Objects navigation in v3
In-Reply-To: <AS8PR05MB76244A63F20D9AB76030287CBA84A@AS8PR05MB7624.eurprd05.prod.outlook.com>
References: <AS8PR05MB76244A63F20D9AB76030287CBA84A@AS8PR05MB7624.eurprd05.prod.outlook.com>
Message-ID: <MN2PR22MB188715CBC0C7BD877DF2ED90F18BA@MN2PR22MB1887.namprd22.prod.outlook.com>

Hello Scott,

You are correct that this is an intentional change in functionality in as of v3.4.0 as a result of all the improvements to the Make Representative functionality. When a digital object instance is selected to display on a resource, archival object, or accession record (as representative), it links to the digital object record from which it came. If a digital object instance is linked but not selected to display, a generic icon appears and goes to the source link instead of the digital object record. (But the image itself won't show on the archival object record because the assumption is that something not marked as representative is not an image to be displayed.)

Whether that could be overridden by a plugin or otherwise, I couldn't say, but others may have good ideas if they have a similar use case.

For anyone interested in getting more familiar with the newer functionality, I recommend the relevant section in the user manual<https://archivesspace.atlassian.net/wiki/spaces/ArchivesSpaceUserManual/pages/3364519945/Make+Representative+Functionality+as+of+v3.4> and the webinar<https://www.youtube.com/watch?v=RfPi8BtFHA4> Jessica Crouch and I did for last summer's Member Forum.

Hope this helps,
Christine

Christine Di Bella
ArchivesSpace Senior Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>

[cid:image001.jpg at 01DA287F.1CA47AF0]


From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Scott Renton
Sent: Wednesday, December 6, 2023 4:52 AM
To: archivesspace_users_group at lyralists.lyrasis.org
Cc: Patryk Smacki <Patryk.Smacki at ed.ac.uk>
Subject: [Archivesspace_Users_Group] Digital Objects navigation in v3

Hi folks

Just about to put our main archives site up from v2.8.1 to v3.4.1. One of our archivists has noticed that where, in the past, she was able to link directly from an image to its source in a native system

(eg https://archives.collections.ed.ac.uk/repositories/2/archival_objects/141060 - the link goes to search results in the LUNA image management system)

she is now forced to go to the digital object first, meaning there's a second click to get there.

Looking at the code, my feeling is that this is a very conscious method of routing in version 3, and it is not something we should look to change (I wouldn't even think the native link is even available to the controller, but rather the digital object id). However, I did think we should check to see if anyone in the community has hit a similar use case and taken any action before we communicate that this is the correct way to work now.

Thanks very much
Scott

PS my colleague Patryk (cc'd) has an outstanding request to register onto the list using the http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group - he's not been accepted in yet though- this is still the way to register?





==========

Scott Renton

Digital Library Development & Systems

Floor F East

Argyle House

515219
The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. Is e buidheann carthannais a th' ann an Oilthigh Dh?n ?ideann, cl?raichte an Alba, ?ireamh cl?raidh SC005336.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231207/9a6f1926/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 56099 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231207/9a6f1926/attachment.jpg>

From Joshua.D.Shaw at dartmouth.edu  Thu Dec  7 08:29:54 2023
From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw)
Date: Thu, 7 Dec 2023 13:29:54 +0000
Subject: [Archivesspace_Users_Group]
	how	to	add	a	new	locale	to	ArchivesSpace?
In-Reply-To: <BL0PR03MB42924E671F6C97F4EA8ADFF6AB84A@BL0PR03MB4292.namprd03.prod.outlook.com>
References: <AM9PR02MB6915A0EFA9E9233D27C3C0A48884A@AM9PR02MB6915.eurprd02.prod.outlook.com>
 <BL0PR03MB429285CBD09CD003B28C4F6AAB84A@BL0PR03MB4292.namprd03.prod.outlook.com>
 <AM9PR02MB6915C05D88CFCC135AC8CF138884A@AM9PR02MB6915.eurprd02.prod.outlook.com>
 <BL0PR03MB429277DEAE0184082B3D4974AB84A@BL0PR03MB4292.namprd03.prod.outlook.com>
 <AM9PR02MB6915C693049E3712B7F54CE48884A@AM9PR02MB6915.eurprd02.prod.outlook.com>
 <BL0PR03MB42928B8DD87506A258957A24AB84A@BL0PR03MB4292.namprd03.prod.outlook.com>
 <BL0PR03MB42924E671F6C97F4EA8ADFF6AB84A@BL0PR03MB4292.namprd03.prod.outlook.com>
Message-ID: <BL0PR03MB4292AEDA561A7B08A36DA3E8AB8BA@BL0PR03MB4292.namprd03.prod.outlook.com>

Because I was curious, I tested this out and created a small plugin that supports this feature: https://github.com/dartmouth-dltg/aspace_custom_localizations

I tested this against 3.4.1, but I believe it will work with most any version of ArchivesSpace.

Hopefully the ReadMe is self explanatory, but let me know if things are unclear.

jds
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Sent: Wednesday, December 6, 2023 4:03 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

The other way to do this (a bit hacky) is to expand the common.jar file in /lib, make your edits to the relevant I18n file (common/aspace_i18n.rb), and then recompress the jar file.

This works for any edits you need to core, but its hacky because its not really a sustainable way to do things since you need to edit the same file for every? update to the core code.

jds


________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Sent: Wednesday, December 6, 2023 1:13 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

One thing you might try is initializing the AppConfig[:locale] setting  in the plugin itself, since it may be an order of operations issue where the main config loads first which attempts to initialize an unknown language (because the plugin hasn't loaded yet).

jds


________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Ron Van den Branden <Ron.VandenBranden at antwerpen.be>
Sent: Wednesday, December 6, 2023 12:00 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

Hi Joshua,

Thanks again for your detailed steps! Although a first attempt didn't work (startup keeps choking on the original languages list), I'm sure we'll get there, with more time. Thanks for pointing me in the good direction: overriding the language list via plugin initialization. I'll definitely check out those other plugins for inspiration.

Best,

Ron


________________________________
Van: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> namens Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Verzonden: woensdag 6 december 2023 17:21
Aan: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Onderwerp: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

U ontvangt niet vaak e-mail van joshua.d.shaw at dartmouth.edu. Meer informatie over waarom dit belangrijk is<https://aka.ms/LearnAboutSenderIdentification>

WAARSCHUWING: DIT IS EEN EXTERNE MAIL

Deze mail komt van buiten onze organisatie. Kijk eerst of je het mailadres en de afzender herkent en/of vertrouwt. Doe dat voor je bijlagen opent of links aanklikt. Zo houden we onze organisatie veiliger voor phishing.

Hey Ron

Here's the way I'd do this.


  1.  Create a new directory in the plugin folder in your ArchivesSpace directory. Call it something like aspace_custom_locatizations (or whatever you want)
  2.  In that new directory, create two new directories: backend and frontend
  3.  In the backend directory, add a file called plugin_init.rb. Put the contents of the monkey patch in that file
  4.  In the frontend directory, add a file tree that mimics the locales directory in the core code:
     *   locales/
     *   locales/enums
  5.  Add your new dutch locales files to those two locations. Name them nl.yml
  6.  In your config file, add your plugin name (the directory name in step 1) to the list of plugins that are active: AppConfig[:plugins] is the key you want to edit.

Since I haven't tested this, there may be some gotchas I'm not thinking about as far as the monkeypatch and where the locales list may also be referenced, but this is the approach I'd take.

There's more info on that tech docs page and there are a bunch of examples to be found on the Awesome ArchivesSpace repo (https://github.com/archivesspace/awesome-archivesspace) and Hudson Molonglo's repos (https://github.com/hudmol) and https://gitlab.gaiaresources.com.au/explor<https://gitlab.gaiaresources.com.au/explore>

jds


________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Ron Van den Branden <Ron.VandenBranden at antwerpen.be>
Sent: Wednesday, December 6, 2023 11:01 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

Hi Joshua,

Ok, thanks for that pointer! The point is that we couldn't find that common/aspace_i18n.rb file in the ArchivesSpace distribution code. Or are you suggesting to add it in a plugin? If so, would you mind guiding me a bit more?

I don't think we've succeeded in building from source (I'm on Windows, so I'm probably at a loss for local testing, I recall some Ruby build incompatibilities).

Best,

Ron

________________________________
Van: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> namens Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Verzonden: woensdag 6 december 2023 16:44
Aan: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Onderwerp: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

U ontvangt niet vaak e-mail van joshua.d.shaw at dartmouth.edu. Meer informatie over waarom dit belangrijk is<https://aka.ms/LearnAboutSenderIdentification>

WAARSCHUWING: DIT IS EEN EXTERNE MAIL

Deze mail komt van buiten onze organisatie. Kijk eerst of je het mailadres en de afzender herkent en/of vertrouwt. Doe dat voor je bijlagen opent of links aanklikt. Zo houden we onze organisatie veiliger voor phishing.

Hey Ron

In addition to what Christine lists....

Off the top of my head (so take with a grain of salt since I haven't actually tested this!)...

In a plugin init (probably a backend plugin_init), monkey patch the self.supported_locales method in common/aspace_i18n.rb. Maybe something like

module I18n
def self.supported_locales
??????enhanced_locales = LOCALES

??????# map I18n language code => ArchivesSpace enumerations:language_iso639_2 code
??????# enumerations iso codes found in common/locales/enums
??????enhanced_locales['nl'] = 'dut'

??????enhanced_locales
end
end

Then you could add your new dutch locale file nl.yml within that same plugin.

OR

You could grab the code tree from github, patch it locally and build your patched application.

Both approaches have their own set of headaches as far as maintenance.

To contribute and other tech docs: https://archivesspace.github.io/tech-docs/readme_develop.html

Hope that helps!
Joshua



________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Ron Van den Branden <Ron.VandenBranden at antwerpen.be>
Sent: Wednesday, December 6, 2023 9:51 AM
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

Hi all,
We're in the process of customizing the ArchivesSpace (3.4.1) staff interface for use in a Dutch-speaking context. We would like to translate the back-end user interface to Dutch. So far, in order to gain speed, we've resorted to tweaking the en.yml localization files with Dutch labels. In the longer run, hijacking "English" for another language feels like a hack, though.
The documentation for "customizing text" at https://archivesspace.github.io/tech-docs/customization/locales.html  does mention where strings can be customized in current locales, but not how new locales can be added. Simply adding new locale files for new languages, with according names and language codes, at the right locations doesn't seem to do the trick:

  *   either the language is not being offered in the list of available languages
  *
when additionally the new language is specified explicitly in the config/config.rb file as AppConfig[:locale] = :nl , this yields following error at startup:

JSONModel::ValidationException: #<:ValidationException: {:errors=>{"defaults/locale"=>["Invalid value 'nl'.  Must be one of: en, fr, de, ja, es"]}}>

                      validate at uri:classloader:/jsonmodel_type.rb:385

            with_validator_for at uri:classloader:/validator_cache.rb:41

...so there must be more to adding a new locale. Yet, we can't find where in the ArchivesSpace distribution code such a list of default locales can be found or edited.
We did find the file in the ArchivesSpace source tree at https://github.com/archivesspace/archivesspace/blob/master/common/aspace_i18n.rb#L28 which defines above list of locales This file can't be found in the distribution code, however, so it's not clear how it relates to the distribution code. The commit history also shows commits from the Weblate project at https://hosted.weblate.org/projects/archivesspace-interfaces/#languages, which contains additional languages Portuguese and Italian.
This leads to following questions:

  *   what's the mechanism for adding a new locale to an ArchivesSpace instance?
  *   if our translations would reach a stage of being of broader interest, what would be the procedure for contributing them?

Kind regards,
Ron


Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis

Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving |  Boeken en Letteren

Minderbroedersstraat 22, 2000 Antwerpen

Grote Markt 1, 2000 Antwerpen

gsm +32 0485 02 80 50 | tel. +32 3 222 93 30

letterenhuis.be<http://www.letterenhuis.be/> | instagram<https://www.instagram.com/letterenhuis/> | facebook<https://www.facebook.com/Letterenhuis>



Proclaimer

Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, niet voor u bestemd is, vragen we u vriendelijk om dat te melden aan de afzender. Deze e-mail en de bijlagen zijn namelijk offici?le documenten van de stad Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie bevatten. Als stad nemen we privacy heel serieus en willen we als een goede huisvader waken over de vertrouwelijkheid van documenten. Als u dit bericht per vergissing hebt ontvangen of ergens hebt gevonden, wees dan zo eerlijk om het meteen te verwijderen en het niet verder te verspreiden of te kopi?ren.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231207/63abe12a/attachment.html>

From jteitelbaum at pabmc.net  Thu Dec  7 10:15:43 2023
From: jteitelbaum at pabmc.net (Teitelbaum, Jesse)
Date: Thu, 7 Dec 2023 15:15:43 +0000
Subject: [Archivesspace_Users_Group] Library
Message-ID: <SA9PR09MB5119D659A889C665068BD2F0A28BA@SA9PR09MB5119.namprd09.prod.outlook.com>

Does anyone use AS for library collections?  I'm trying to find a way to include our library books so they can be included in search results.  I don't really want to have a separate database for books, having researchers needing to search multiple resources.

Jesse Teitelbaum | Director of Archives
Pennsylvania House of Representatives
628 Irvis Office Building | Harrisburg PA 17120
Phone: 717.783.3866
Email: jteitelbaum at pabmc.net<mailto:jteitelbaum at pabmc.net>
https://archives.house.state.pa.us<https://archives.house.state.pa.us/>
 [cid:image001.png at 01DA28F6.55755670]
PLEASE BE ADVISED: The information in this message is intended solely for the addressee. This message may contain confidential and/or privileged information. If you are not the intended recipient of this message, any disclosure, copying, distribution of this message is strictly prohibited. If you have received this message erroneously, please delete all copies of it, as well as any attachments, and notify me by reply e-mail immediately. Thank you.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231207/d69d41f5/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 34455 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231207/d69d41f5/attachment.png>

From Scott.Renton at ed.ac.uk  Thu Dec  7 11:58:54 2023
From: Scott.Renton at ed.ac.uk (Scott Renton)
Date: Thu, 7 Dec 2023 16:58:54 +0000
Subject: [Archivesspace_Users_Group] Digital Objects navigation in v3
In-Reply-To: <MN2PR22MB188715CBC0C7BD877DF2ED90F18BA@MN2PR22MB1887.namprd22.prod.outlook.com>
References: <AS8PR05MB76244A63F20D9AB76030287CBA84A@AS8PR05MB7624.eurprd05.prod.outlook.com>
 <MN2PR22MB188715CBC0C7BD877DF2ED90F18BA@MN2PR22MB1887.namprd22.prod.outlook.com>
Message-ID: <AS8PR05MB76244410730907317D017355BA8BA@AS8PR05MB7624.eurprd05.prod.outlook.com>

Thanks Christina, much appreciated- I'll feed this back.

Cheers
Scott



==========

Scott Renton

Digital Library Development & Systems

Floor F East

Argyle House

515219

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Christine Di Bella <christine.dibella at lyrasis.org>
Sent: 07 December 2023 01:02
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Cc: Patryk Smacki <Patryk.Smacki at ed.ac.uk>
Subject: Re: [Archivesspace_Users_Group] Digital Objects navigation in v3

This email was sent to you by someone outside the University.
You should only click on links or attachments if you are certain that the email is genuine and the content is safe.

Hello Scott,



You are correct that this is an intentional change in functionality in as of v3.4.0 as a result of all the improvements to the Make Representative functionality. When a digital object instance is selected to display on a resource, archival object, or accession record (as representative), it links to the digital object record from which it came. If a digital object instance is linked but not selected to display, a generic icon appears and goes to the source link instead of the digital object record. (But the image itself won?t show on the archival object record because the assumption is that something not marked as representative is not an image to be displayed.)



Whether that could be overridden by a plugin or otherwise, I couldn?t say, but others may have good ideas if they have a similar use case.



For anyone interested in getting more familiar with the newer functionality, I recommend the relevant section in the user manual<https://archivesspace.atlassian.net/wiki/spaces/ArchivesSpaceUserManual/pages/3364519945/Make+Representative+Functionality+as+of+v3.4> and the webinar<https://www.youtube.com/watch?v=RfPi8BtFHA4> Jessica Crouch and I did for last summer?s Member Forum.



Hope this helps,

Christine



Christine Di Bella

ArchivesSpace Senior Program Manager

christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>



[cid:image001.jpg at 01DA287F.1CA47AF0]





From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Scott Renton
Sent: Wednesday, December 6, 2023 4:52 AM
To: archivesspace_users_group at lyralists.lyrasis.org
Cc: Patryk Smacki <Patryk.Smacki at ed.ac.uk>
Subject: [Archivesspace_Users_Group] Digital Objects navigation in v3



Hi folks



Just about to put our main archives site up from v2.8.1 to v3.4.1. One of our archivists has noticed that where, in the past, she was able to link directly from an image to its source in a native system



(eg https://archives.collections.ed.ac.uk/repositories/2/archival_objects/141060 - the link goes to search results in the LUNA image management system)



she is now forced to go to the digital object first, meaning there's a second click to get there.



Looking at the code, my feeling is that this is a very conscious method of routing in version 3, and it is not something we should look to change (I wouldn't even think the native link is even available to the controller, but rather the digital object id). However, I did think we should check to see if anyone in the community has hit a similar use case and taken any action before we communicate that this is the correct way to work now.



Thanks very much
Scott



PS my colleague Patryk (cc'd) has an outstanding request to register onto the list using the http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group - he's not been accepted in yet though- this is still the way to register?







==========

Scott Renton

Digital Library Development & Systems

Floor F East

Argyle House

515219

The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. Is e buidheann carthannais a th? ann an Oilthigh Dh?n ?ideann, cl?raichte an Alba, ?ireamh cl?raidh SC005336.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231207/f39a5cdd/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 56099 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231207/f39a5cdd/attachment-0001.jpg>

From ahetley at pbvmsf.org  Thu Dec  7 12:45:59 2023
From: ahetley at pbvmsf.org (Andrea Hetley)
Date: Thu, 7 Dec 2023 17:45:59 +0000
Subject: [Archivesspace_Users_Group] Library
In-Reply-To: <SA9PR09MB5119D659A889C665068BD2F0A28BA@SA9PR09MB5119.namprd09.prod.outlook.com>
References: <SA9PR09MB5119D659A889C665068BD2F0A28BA@SA9PR09MB5119.namprd09.prod.outlook.com>
Message-ID: <SJ0PR08MB7833A7BAC6EA02F81E5A19D2DA8BA@SJ0PR08MB7833.namprd08.prod.outlook.com>

I do include the small collection of books in our ArchivesSpace.  I enter each one as an item, and they have their own series within a record group called Special Collections.

Here is a screenshot of one such record, if it helps.

[A screenshot of a computer  Description automatically generated]

Andrea Hetley
Archivist
Sisters of the Presentation, San Francisco
281 Masonic Avenue, San Francisco, CA 94108-4416
(415) 751-0406 Office

[page9image20086208]

Serving the people of God in the San Francisco Bay Area since 1854.

eNewsletter: bit.ly/GetPresLight | Presentationsisterssf.org  | Facebook.com/PBVMSF


From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Teitelbaum, Jesse <jteitelbaum at pabmc.net>
Date: Thursday, December 7, 2023 at 7:20?AM
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Library
Does anyone use AS for library collections?  I?m trying to find a way to include our library books so they can be included in search results.  I don?t really want to have a separate database for books, having researchers needing to search multiple resources.

Jesse Teitelbaum | Director of Archives
Pennsylvania House of Representatives
628 Irvis Office Building | Harrisburg PA 17120
Phone: 717.783.3866
Email: jteitelbaum at pabmc.net<mailto:jteitelbaum at pabmc.net>
https://archives.house.state.pa.us<https://archives.house.state.pa.us/>
 [cid:image001.png at 01DA28F6.55755670]
PLEASE BE ADVISED: The information in this message is intended solely for the addressee. This message may contain confidential and/or privileged information. If you are not the intended recipient of this message, any disclosure, copying, distribution of this message is strictly prohibited. If you have received this message erroneously, please delete all copies of it, as well as any attachments, and notify me by reply e-mail immediately. Thank you.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231207/7369259c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 34455 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231207/7369259c/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 82525 bytes
Desc: image002.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231207/7369259c/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 219236 bytes
Desc: image003.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231207/7369259c/attachment.jpg>

From Joshua.D.Shaw at dartmouth.edu  Thu Dec  7 13:27:24 2023
From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw)
Date: Thu, 7 Dec 2023 18:27:24 +0000
Subject: [Archivesspace_Users_Group]
	how	to	add	a	new	locale	to	ArchivesSpace?
In-Reply-To: <BL0PR03MB4292AEDA561A7B08A36DA3E8AB8BA@BL0PR03MB4292.namprd03.prod.outlook.com>
References: <AM9PR02MB6915A0EFA9E9233D27C3C0A48884A@AM9PR02MB6915.eurprd02.prod.outlook.com>
 <BL0PR03MB429285CBD09CD003B28C4F6AAB84A@BL0PR03MB4292.namprd03.prod.outlook.com>
 <AM9PR02MB6915C05D88CFCC135AC8CF138884A@AM9PR02MB6915.eurprd02.prod.outlook.com>
 <BL0PR03MB429277DEAE0184082B3D4974AB84A@BL0PR03MB4292.namprd03.prod.outlook.com>
 <AM9PR02MB6915C693049E3712B7F54CE48884A@AM9PR02MB6915.eurprd02.prod.outlook.com>
 <BL0PR03MB42928B8DD87506A258957A24AB84A@BL0PR03MB4292.namprd03.prod.outlook.com>
 <BL0PR03MB42924E671F6C97F4EA8ADFF6AB84A@BL0PR03MB4292.namprd03.prod.outlook.com>
 <BL0PR03MB4292AEDA561A7B08A36DA3E8AB8BA@BL0PR03MB4292.namprd03.prod.outlook.com>
Message-ID: <BL0PR03MB4292F6FEF2F942C7E67A3C38AB8BA@BL0PR03MB4292.namprd03.prod.outlook.com>

I'm working with Ron to resolve a couple of issues with the plugin and will report back when those are sorted.

jds

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Sent: Thursday, December 7, 2023 8:29 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

Because I was curious, I tested this out and created a small plugin that supports this feature: https://github.com/dartmouth-dltg/aspace_custom_localizations

I tested this against 3.4.1, but I believe it will work with most any version of ArchivesSpace.

Hopefully the ReadMe is self explanatory, but let me know if things are unclear.

jds
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Sent: Wednesday, December 6, 2023 4:03 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

The other way to do this (a bit hacky) is to expand the common.jar file in /lib, make your edits to the relevant I18n file (common/aspace_i18n.rb), and then recompress the jar file.

This works for any edits you need to core, but its hacky because its not really a sustainable way to do things since you need to edit the same file for every? update to the core code.

jds


________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Sent: Wednesday, December 6, 2023 1:13 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

One thing you might try is initializing the AppConfig[:locale] setting  in the plugin itself, since it may be an order of operations issue where the main config loads first which attempts to initialize an unknown language (because the plugin hasn't loaded yet).

jds


________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Ron Van den Branden <Ron.VandenBranden at antwerpen.be>
Sent: Wednesday, December 6, 2023 12:00 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

Hi Joshua,

Thanks again for your detailed steps! Although a first attempt didn't work (startup keeps choking on the original languages list), I'm sure we'll get there, with more time. Thanks for pointing me in the good direction: overriding the language list via plugin initialization. I'll definitely check out those other plugins for inspiration.

Best,

Ron


________________________________
Van: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> namens Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Verzonden: woensdag 6 december 2023 17:21
Aan: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Onderwerp: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

U ontvangt niet vaak e-mail van joshua.d.shaw at dartmouth.edu. Meer informatie over waarom dit belangrijk is<https://aka.ms/LearnAboutSenderIdentification>

WAARSCHUWING: DIT IS EEN EXTERNE MAIL

Deze mail komt van buiten onze organisatie. Kijk eerst of je het mailadres en de afzender herkent en/of vertrouwt. Doe dat voor je bijlagen opent of links aanklikt. Zo houden we onze organisatie veiliger voor phishing.

Hey Ron

Here's the way I'd do this.


  1.  Create a new directory in the plugin folder in your ArchivesSpace directory. Call it something like aspace_custom_locatizations (or whatever you want)
  2.  In that new directory, create two new directories: backend and frontend
  3.  In the backend directory, add a file called plugin_init.rb. Put the contents of the monkey patch in that file
  4.  In the frontend directory, add a file tree that mimics the locales directory in the core code:
     *   locales/
     *   locales/enums
  5.  Add your new dutch locales files to those two locations. Name them nl.yml
  6.  In your config file, add your plugin name (the directory name in step 1) to the list of plugins that are active: AppConfig[:plugins] is the key you want to edit.

Since I haven't tested this, there may be some gotchas I'm not thinking about as far as the monkeypatch and where the locales list may also be referenced, but this is the approach I'd take.

There's more info on that tech docs page and there are a bunch of examples to be found on the Awesome ArchivesSpace repo (https://github.com/archivesspace/awesome-archivesspace) and Hudson Molonglo's repos (https://github.com/hudmol) and https://gitlab.gaiaresources.com.au/explor<https://gitlab.gaiaresources.com.au/explore>

jds


________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Ron Van den Branden <Ron.VandenBranden at antwerpen.be>
Sent: Wednesday, December 6, 2023 11:01 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

Hi Joshua,

Ok, thanks for that pointer! The point is that we couldn't find that common/aspace_i18n.rb file in the ArchivesSpace distribution code. Or are you suggesting to add it in a plugin? If so, would you mind guiding me a bit more?

I don't think we've succeeded in building from source (I'm on Windows, so I'm probably at a loss for local testing, I recall some Ruby build incompatibilities).

Best,

Ron

________________________________
Van: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> namens Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Verzonden: woensdag 6 december 2023 16:44
Aan: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Onderwerp: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

U ontvangt niet vaak e-mail van joshua.d.shaw at dartmouth.edu. Meer informatie over waarom dit belangrijk is<https://aka.ms/LearnAboutSenderIdentification>

WAARSCHUWING: DIT IS EEN EXTERNE MAIL

Deze mail komt van buiten onze organisatie. Kijk eerst of je het mailadres en de afzender herkent en/of vertrouwt. Doe dat voor je bijlagen opent of links aanklikt. Zo houden we onze organisatie veiliger voor phishing.

Hey Ron

In addition to what Christine lists....

Off the top of my head (so take with a grain of salt since I haven't actually tested this!)...

In a plugin init (probably a backend plugin_init), monkey patch the self.supported_locales method in common/aspace_i18n.rb. Maybe something like

module I18n
def self.supported_locales
??????enhanced_locales = LOCALES

??????# map I18n language code => ArchivesSpace enumerations:language_iso639_2 code
??????# enumerations iso codes found in common/locales/enums
??????enhanced_locales['nl'] = 'dut'

??????enhanced_locales
end
end

Then you could add your new dutch locale file nl.yml within that same plugin.

OR

You could grab the code tree from github, patch it locally and build your patched application.

Both approaches have their own set of headaches as far as maintenance.

To contribute and other tech docs: https://archivesspace.github.io/tech-docs/readme_develop.html

Hope that helps!
Joshua



________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Ron Van den Branden <Ron.VandenBranden at antwerpen.be>
Sent: Wednesday, December 6, 2023 9:51 AM
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

Hi all,
We're in the process of customizing the ArchivesSpace (3.4.1) staff interface for use in a Dutch-speaking context. We would like to translate the back-end user interface to Dutch. So far, in order to gain speed, we've resorted to tweaking the en.yml localization files with Dutch labels. In the longer run, hijacking "English" for another language feels like a hack, though.
The documentation for "customizing text" at https://archivesspace.github.io/tech-docs/customization/locales.html  does mention where strings can be customized in current locales, but not how new locales can be added. Simply adding new locale files for new languages, with according names and language codes, at the right locations doesn't seem to do the trick:

  *   either the language is not being offered in the list of available languages
  *
when additionally the new language is specified explicitly in the config/config.rb file as AppConfig[:locale] = :nl , this yields following error at startup:

JSONModel::ValidationException: #<:ValidationException: {:errors=>{"defaults/locale"=>["Invalid value 'nl'.  Must be one of: en, fr, de, ja, es"]}}>

                      validate at uri:classloader:/jsonmodel_type.rb:385

            with_validator_for at uri:classloader:/validator_cache.rb:41

...so there must be more to adding a new locale. Yet, we can't find where in the ArchivesSpace distribution code such a list of default locales can be found or edited.
We did find the file in the ArchivesSpace source tree at https://github.com/archivesspace/archivesspace/blob/master/common/aspace_i18n.rb#L28 which defines above list of locales This file can't be found in the distribution code, however, so it's not clear how it relates to the distribution code. The commit history also shows commits from the Weblate project at https://hosted.weblate.org/projects/archivesspace-interfaces/#languages, which contains additional languages Portuguese and Italian.
This leads to following questions:

  *   what's the mechanism for adding a new locale to an ArchivesSpace instance?
  *   if our translations would reach a stage of being of broader interest, what would be the procedure for contributing them?

Kind regards,
Ron


Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis

Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving |  Boeken en Letteren

Minderbroedersstraat 22, 2000 Antwerpen

Grote Markt 1, 2000 Antwerpen

gsm +32 0485 02 80 50 | tel. +32 3 222 93 30

letterenhuis.be<http://www.letterenhuis.be/> | instagram<https://www.instagram.com/letterenhuis/> | facebook<https://www.facebook.com/Letterenhuis>



Proclaimer

Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, niet voor u bestemd is, vragen we u vriendelijk om dat te melden aan de afzender. Deze e-mail en de bijlagen zijn namelijk offici?le documenten van de stad Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie bevatten. Als stad nemen we privacy heel serieus en willen we als een goede huisvader waken over de vertrouwelijkheid van documenten. Als u dit bericht per vergissing hebt ontvangen of ergens hebt gevonden, wees dan zo eerlijk om het meteen te verwijderen en het niet verder te verspreiden of te kopi?ren.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231207/40f28fb4/attachment.html>

From christine.dibella at lyrasis.org  Thu Dec  7 15:38:12 2023
From: christine.dibella at lyrasis.org (Christine Di Bella)
Date: Thu, 7 Dec 2023 20:38:12 +0000
Subject: [Archivesspace_Users_Group] Bulk import of DOs with multiple
	file	versions
In-Reply-To: <MEYPR01MB73402B89CA95834628EF9531A385A@MEYPR01MB7340.ausprd01.prod.outlook.com>
References: <MEYPR01MB73402B89CA95834628EF9531A385A@MEYPR01MB7340.ausprd01.prod.outlook.com>
Message-ID: <MN2PR22MB1887058A33DC84CCF20C0B4DF18BA@MN2PR22MB1887.namprd22.prod.outlook.com>

Hello William,

You are correct that the Digital Objects CSV is not designed to support the import of more than one file version per digital object. The bulk import templates support importing two file versions, but as you note, they are for creating digital objects that as associated with archival objects.

One alternative would be to use the API to create digital objects. This would allow you create as many file versions as you wish per digital object. People here may have some good tips or scripts for that, or suggestions of other strategies for doing what you want to do.

Christine

Christine Di Bella
ArchivesSpace Senior Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>

[cid:image001.jpg at 01DA28DE.B7C65490]



From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of William Hamill
Sent: Tuesday, December 5, 2023 2:55 PM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Bulk import of DOs with multiple file versions

Kia ora koutou,

I?m hoping someone out there may be able to offer some pointers on doing a bulk import of Digital Object records.

Using the aspace_digital_object_template.csv works fine as it is, but the records I would like to create typically have 2-3 file versions. I?ve tried copying the file version columns and adding ?_1? and ?_2? to various places, but the importer just skips those columns altogether and I get a record with no file versions at all.

Is this just a case of user error, or does the import template not work with multiple file versions? We?re running AS ver.3.3.1

Note that I?m just wanting to create the digital objects at this stage ? not import associating with an archival object (also, that importer seems to just have linked out object and thumbnail settings that don?t suit).

Any tips would be great,

Thanks very much

William Hamill
Team Leader ? Cultural Collections
Archive of M?ori and Pacific Sound
Te Tumu Herenga | Libraries and Learning Services
Waipapa Taumata Rau | University of Auckland
w.hamill at auckland.ac.nz<mailto:w.hamill at auckland.ac.nz>
Ph: (64 9) 373 7599 ext. 85733
DDI: (64 9) 923 5733

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231207/ea0d7b3a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 56099 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231207/ea0d7b3a/attachment.jpg>

From li_yanlin at fudan.edu.cn  Fri Dec  8 02:38:06 2023
From: li_yanlin at fudan.edu.cn (=?UTF-8?B?5p2O5b2m6ZyW?=)
Date: Fri, 8 Dec 2023 15:38:06 +0800 (GMT+08:00)
Subject: [Archivesspace_Users_Group] Library
In-Reply-To: <SA9PR09MB5119D659A889C665068BD2F0A28BA@SA9PR09MB5119.namprd09.prod.outlook.com>
References: <SA9PR09MB5119D659A889C665068BD2F0A28BA@SA9PR09MB5119.namprd09.prod.outlook.com>
Message-ID: <71492fa7.264d3.18c485cbd2d.Coremail.li_yanlin@fudan.edu.cn>

I do it, too. But more like a research guide.




??? "Ellen" Yanlin Li

???? Special Collections Librarian/Archivist

??????? Fudan University Library

Li_yanlin at fudan.edu.cn

drlidekelaiden at gmail.com 

-----????-----
???:"Teitelbaum, Jesse" <jteitelbaum at pabmc.net>
????:2023-12-07 23:15:43 (???)
???: "archivesspace_users_group at lyralists.lyrasis.org" <archivesspace_users_group at lyralists.lyrasis.org>
??: [Archivesspace_Users_Group] Library



Does anyone use AS for library collections?  I?m trying to find a way to include our library books so they can be included in search results.  I don?t really want to have a separate database for books, having researchers needing to search multiple resources.

 

Jesse Teitelbaum | Director of Archives

Pennsylvania House of Representatives

628 Irvis Office Building | Harrisburg PA 17120

Phone: 717.783.3866
Email: jteitelbaum at pabmc.net

https://archives.house.state.pa.us

 

PLEASE BE ADVISED: The information in this message is intended solely for the addressee. This message may contain confidential and/or privileged information. If you are not the intended recipient of this message, any disclosure, copying, distribution of this message is strictly prohibited. If you have received this message erroneously, please delete all copies of it, as well as any attachments, and notify me by reply e-mail immediately. Thank you.

 




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231208/ce527841/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 34455 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231208/ce527841/attachment.png>

From mpaquette at smith.edu  Fri Dec  8 14:39:15 2023
From: mpaquette at smith.edu (Michelle Paquette)
Date: Fri, 8 Dec 2023 14:39:15 -0500
Subject: [Archivesspace_Users_Group] Bulk import of DOs with multiple
	file versions
In-Reply-To: <MN2PR22MB1887058A33DC84CCF20C0B4DF18BA@MN2PR22MB1887.namprd22.prod.outlook.com>
References: <MEYPR01MB73402B89CA95834628EF9531A385A@MEYPR01MB7340.ausprd01.prod.outlook.com>
 <MN2PR22MB1887058A33DC84CCF20C0B4DF18BA@MN2PR22MB1887.namprd22.prod.outlook.com>
Message-ID: <CANgF2Fs1Qs88BUTXjspsoY13EMcift=-cDd0s3soQRik+esxMg@mail.gmail.com>

William, if you have access to the API I do this kind of batch addition of
digital objects frequently and would be happy to help you out. Feel free to
reach out.

Best,
Michelle

On Thu, Dec 7, 2023 at 3:38?PM Christine Di Bella <
christine.dibella at lyrasis.org> wrote:

> Hello William,
>
>
>
> You are correct that the Digital Objects CSV is not designed to support
> the import of more than one file version per digital object. The bulk
> import templates support importing two file versions, but as you note, they
> are for creating digital objects that as associated with archival objects.
>
>
>
> One alternative would be to use the API to create digital objects. This
> would allow you create as many file versions as you wish per digital
> object. People here may have some good tips or scripts for that, or
> suggestions of other strategies for doing what you want to do.
>
>
>
> Christine
>
>
>
> Christine Di Bella
>
> ArchivesSpace Senior Program Manager
>
> christine.dibella at lyrasis.org
>
>
>
>
>
>
>
>
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org <
> archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *William
> Hamill
> *Sent:* Tuesday, December 5, 2023 2:55 PM
> *To:* archivesspace_users_group at lyralists.lyrasis.org
> *Subject:* [Archivesspace_Users_Group] Bulk import of DOs with multiple
> file versions
>
>
>
> Kia ora koutou,
>
>
>
> I?m hoping someone out there may be able to offer some pointers on doing a
> bulk import of Digital Object records.
>
>
>
> Using the aspace_digital_object_template.csv works fine as it is, but the
> records I would like to create typically have 2-3 file versions. I?ve tried
> copying the file version columns and adding ?_1? and ?_2? to various
> places, but the importer just skips those columns altogether and I get a
> record with no file versions at all.
>
>
>
> Is this just a case of user error, or does the import template not work
> with multiple file versions? We?re running AS ver.3.3.1
>
>
>
> Note that I?m just wanting to create the digital objects at this stage ?
> not import associating with an archival object (also, that importer seems
> to just have linked out object and thumbnail settings that don?t suit).
>
>
>
> Any tips would be great,
>
>
>
> Thanks very much
>
>
>
> *William Hamill*
>
> *Team Leader ? Cultural Collections*
>
> Archive of M?ori and Pacific Sound
>
> Te Tumu Herenga | Libraries and Learning Services
>
> Waipapa Taumata Rau | University of Auckland
>
> w.hamill at auckland.ac.nz
>
> Ph: (64 9) 373 7599 ext. 85733
>
> DDI: (64 9) 923 5733
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>


-- 
Michelle Paquette
(she/her)
Metadata & Technical Services Archivist
Special Collections
Smith College
413-585-7029
mpaquette at smith.edu

For current library access and services details, see Library Services
During COVID-19
<https://libraries.smith.edu/library-services-during-covid-19>.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231208/8e9fee79/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 56099 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231208/8e9fee79/attachment-0001.jpg>

From bailey-grace.harrell at lyrasis.org  Mon Dec 11 07:50:52 2023
From: bailey-grace.harrell at lyrasis.org (Bailey-Grace Harrell)
Date: Mon, 11 Dec 2023 12:50:52 +0000
Subject: [Archivesspace_Users_Group] Reminder: Virtual Member Forum | Save
 the Date and Call for Planning Team Members
Message-ID: <CYYPR22MB4158B41A9ABC5ECD64CD400DC68FA@CYYPR22MB4158.namprd22.prod.outlook.com>

ArchivesSpace Virtual Member Forum 2024 - Save the Date and Call for Planning Team Members

Mark your calendars for our 2024 Virtual Member Forum! Taking place March 26-27, 2024, our Virtual Member Forum will be a two-day event spanning a variety of time zones and ArchivesSpace experience levels.

If you are interested in serving on the planning team for this forum, please email Jessica Crouch atjessica.crouch at lyrasis.org<mailto:jessica.crouch at lyrasis.org> by December 8, 2023.  The Virtual Member Forum is one of our largest events of the year and we are looking for volunteers to review proposals, develop the schedule, and help make this forum great!

More information will be provided soon about how to propose a topic or presentation.  Registration will open closer to the event date.  For now, be sure to save the date on your calendar.  We look forward to ?seeing? many of you there.

Best,

Bailey-Grace Harrell
ArchivesSpace Program Assistant
Bailey-grace.harrell at lyrasis.com<mailto:Bailey-grace.harrell at lyrasis.com>

[signature_1033522931]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231211/20688013/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 224996 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231211/20688013/attachment.png>

From shand at ap.org  Mon Dec 11 12:41:50 2023
From: shand at ap.org (Hand, Sarit)
Date: Mon, 11 Dec 2023 17:41:50 +0000
Subject: [Archivesspace_Users_Group] Library
In-Reply-To: <SJ0PR08MB7833A7BAC6EA02F81E5A19D2DA8BA@SJ0PR08MB7833.namprd08.prod.outlook.com>
References: <SA9PR09MB5119D659A889C665068BD2F0A28BA@SA9PR09MB5119.namprd09.prod.outlook.com>
 <SJ0PR08MB7833A7BAC6EA02F81E5A19D2DA8BA@SJ0PR08MB7833.namprd08.prod.outlook.com>
Message-ID: <BL0PR16MB2419D0DE42530A9F21387CCBCF8FA@BL0PR16MB2419.namprd16.prod.outlook.com>

Hi!

I just completed a project cataloguing our reference library into ASpace. I posted a couple of questions in this list, you can look for them and see what responses I got.

I created a single resource record for our library and a child record per book as an item.
[cid:image004.png at 01DA2C2A.14CB5750]

I utilized sub-records for the bibliographic data, i.e. publication and date, authors and Notes.

As an example of notes I used: The data comes from a legacy database and required a lot of cleanup to get to this point. The abstract currently reflects subject heading and agents as subjects.  A later project will be to utilize actual subject and agent links. Whereas, currently, Agent links only reflect authors and editors (creators).
[cid:image001.png at 01DA2C2F.433CE400]
If you want more details, feel free to reach out.

Cheers,
[cid:image005.png at 01DA2C2A.14CB5750]                                              [cid:image006.jpg at 01DA2C2A.14CB5750]
Sarit Hand                                                       200 Liberty St.
Digital Archivist                                               New York, NY 10281
Corporate Archives                                         T 212.621.7035


shand at ap.org
www.ap.org<http://www.ap.org/>
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Andrea Hetley
Sent: Thursday, December 7, 2023 12:46 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Library

You don't often get email from ahetley at pbvmsf.org<mailto:ahetley at pbvmsf.org>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>

[EXTERNAL]
I do include the small collection of books in our ArchivesSpace.  I enter each one as an item, and they have their own series within a record group called Special Collections.

Here is a screenshot of one such record, if it helps.

[A screenshot of a computer  Description automatically generated]

Andrea Hetley
Archivist
Sisters of the Presentation, San Francisco
281 Masonic Avenue, San Francisco, CA 94108-4416
(415) 751-0406 Office

[page9image20086208]

Serving the people of God in the San Francisco Bay Area since 1854.

eNewsletter: bit.ly/GetPresLight | Presentationsisterssf.org  | Facebook.com/PBVMSF


From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Teitelbaum, Jesse <jteitelbaum at pabmc.net<mailto:jteitelbaum at pabmc.net>>
Date: Thursday, December 7, 2023 at 7:20?AM
To: archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org> <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Library
Does anyone use AS for library collections?  I?m trying to find a way to include our library books so they can be included in search results.  I don?t really want to have a separate database for books, having researchers needing to search multiple resources.

Jesse Teitelbaum | Director of Archives
Pennsylvania House of Representatives
628 Irvis Office Building | Harrisburg PA 17120
Phone: 717.783.3866
Email: jteitelbaum at pabmc.net<mailto:jteitelbaum at pabmc.net>
https://archives.house.state.pa.us<https://archives.house.state.pa.us/>
 [cid:image009.png at 01DA2C2A.14CB5750]
PLEASE BE ADVISED: The information in this message is intended solely for the addressee. This message may contain confidential and/or privileged information. If you are not the intended recipient of this message, any disclosure, copying, distribution of this message is strictly prohibited. If you have received this message erroneously, please delete all copies of it, as well as any attachments, and notify me by reply e-mail immediately. Thank you.

The information contained in this communication is intended for the use of the designated recipients named above. If the reader of this communication is not the intended recipient, you are hereby notified that you have received this communication in error, and that any review, dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify The Associated Press immediately by telephone at +1-212-621-1500 and delete this email. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231211/dad65464/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 18047 bytes
Desc: image004.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231211/dad65464/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 5729 bytes
Desc: image005.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231211/dad65464/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.jpg
Type: image/jpeg
Size: 1715 bytes
Desc: image006.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231211/dad65464/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.jpg
Type: image/jpeg
Size: 219236 bytes
Desc: image007.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231211/dad65464/attachment-0003.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.png
Type: image/png
Size: 82525 bytes
Desc: image008.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231211/dad65464/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image009.png
Type: image/png
Size: 34455 bytes
Desc: image009.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231211/dad65464/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 21154 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231211/dad65464/attachment-0009.png>

From cnorton9 at library.rochester.edu  Tue Dec 12 16:02:21 2023
From: cnorton9 at library.rochester.edu (Norton, Channing)
Date: Tue, 12 Dec 2023 21:02:21 +0000
Subject: [Archivesspace_Users_Group] Search Tuning
Message-ID: <5e7a5342-2880-4109-8b21-985991a7293f@ur.rochester.edu>

User group,

Rochester is looking to improve our search results. We know there's 
limited configuration available in the ArchivesSpace config.rb file, but 
that's where we are able to make changes. Would anyone who is happy with 
how their search is configured be willing to share the relevant stanzas 
from their config.rb? Especially interested in other Lyrasis customers, 
as presumably the Solr server will be configured the same for each.

-- 
Channing Norton (He/Him/They/Them)

Senior Programmer Analyst

Digital Initiatives

University of Rochester

  

On Campus Tues, Wed


From Ron.VandenBranden at antwerpen.be  Wed Dec 13 05:26:27 2023
From: Ron.VandenBranden at antwerpen.be (Ron Van den Branden)
Date: Wed, 13 Dec 2023 10:26:27 +0000
Subject: [Archivesspace_Users_Group] What's the status of the as_history
	plugin?
Message-ID: <AM9PR02MB691512B2BBBA191CCA5A926A888DA@AM9PR02MB6915.eurprd02.prod.outlook.com>

Hi all,

I've been able to set up a local ArchivesSpace test instance and am diving into the treasury of available plugins. On top of my list was the as_history plugin (https://gitlab.gaiaresources.com.au/qsa/as_history).

In short, I'm wondering what its status is. From a previous exchange in May on this mailing list (http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2023-May/010003.html), I recall how James Bullow added the disclaimer that the public version was tied to the specific context in which it had been developed and probably won't work in other contexts. Yet, installing and browsing records' history works like a charm, only restoring previous versions throws an error.

Since most of it seems to work surprisingly well, I'd like to know if it has been developed further and is ready for the "outside world". If so:

  *
would this mailing list be the place to report bugs, or would the Gitlab issue tracker be the best forum?
  *
has it been used on a large scale? We're migrating a repo of about 2k resources, 190k archival objects, 69k agents into ArchivesSpace. I know as_history will only start logging the history from that migration onward, but I can imagine the history for such an amount of records would be considerable. Is it feasible to use as_history for this magnitude of data?

Best,

Ron



Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis

Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving |  Boeken en Letteren

Minderbroedersstraat 22, 2000 Antwerpen

Grote Markt 1, 2000 Antwerpen

gsm +32 0485 02 80 50 | tel. +32 3 222 93 30

letterenhuis.be<http://www.letterenhuis.be/> | instagram<https://www.instagram.com/letterenhuis/> | facebook<https://www.facebook.com/Letterenhuis>



Proclaimer

Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, niet voor u bestemd is, vragen we u vriendelijk om dat te melden aan de afzender. Deze e-mail en de bijlagen zijn namelijk offici?le documenten van de stad Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie bevatten. Als stad nemen we privacy heel serieus en willen we als een goede huisvader waken over de vertrouwelijkheid van documenten. Als u dit bericht per vergissing hebt ontvangen of ergens hebt gevonden, wees dan zo eerlijk om het meteen te verwijderen en het niet verder te verspreiden of te kopi?ren.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231213/3596a785/attachment.html>

From Ludwig at frick.org  Wed Dec 13 16:43:44 2023
From: Ludwig at frick.org (Ludwig, Julie)
Date: Wed, 13 Dec 2023 21:43:44 +0000
Subject: [Archivesspace_Users_Group] Orange Logic integration
Message-ID: <SA0PR17MB4506457AD3E992AAE1C71337DF8DA@SA0PR17MB4506.namprd17.prod.outlook.com>

Hello,
We are in the process of migrating into Orange Logic as our new DAMS, and are hoping to integrate this system with ASpace.  Has anyone else integrated these two platforms?  If not Orange Logic, we'd be interested in seeing examples of ASpace integrations with other DAMS.

Thanks very much,
Julie Ludwig


Julie A. Ludwig
Archivist
The Frick Collection
Frick Art Reference Library
ludwig at frick.org<mailto:ludwig at frick.org>

Visit our temporary home at
945 Madison Avenue at 75th Street

[cid:image001.png at 01DA2D05.3BEC01A0]<https://www.frick.org/>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231213/cb1fe221/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 6552 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231213/cb1fe221/attachment.png>

From james at hudmol.com  Wed Dec 13 17:48:59 2023
From: james at hudmol.com (James Bullen)
Date: Thu, 14 Dec 2023 09:48:59 +1100
Subject: [Archivesspace_Users_Group] What's the status of the as_history
	plugin?
In-Reply-To: <AM9PR02MB691512B2BBBA191CCA5A926A888DA@AM9PR02MB6915.eurprd02.prod.outlook.com>
References: <AM9PR02MB691512B2BBBA191CCA5A926A888DA@AM9PR02MB6915.eurprd02.prod.outlook.com>
Message-ID: <FF5DC08F-67CF-410E-8670-4E303859AF42@hudmol.com>


Hi Ron,

We developed the as_history plugin as part of the Queensland State Archives Digital Archiving Program.

It has been running in production as part of that system for a few years. The QSA instance of ArchivesSpace is a very heavily customized fork from v2.5-ish. Many changes in our fork have found their way into AS core code - bug fixes, optimizations and enhancements. One of those changes was required for the open source version of as_history to work. Now that that change is in AS, as_history should more or less work correctly with vanilla AS.

However, the plugin is maintained exclusively to function as part of the QSA system, so we still don?t recommend using it in production.

To your questions:
Since as_history is maintained as part of the QSA system, it doesn?t really make sense to report bugs discovered when running it out of that context. If you find some problems, or have some suggestions for enhancements, or indeed, any contributions, it is probably best just to email me.
The QSA system has millions of records. The plugin has been running successfully as part of that system for a few years. So, yes, it has been proven to work at scale.


Cheers,
James


?
James Bullen
Director/Developer
Hudson Molonglo
hudsonmolonglo.com <http://hudsonmolonglo.com/>
?



> On Dec 13, 2023, at 9:26?PM, Ron Van den Branden <Ron.VandenBranden at antwerpen.be> wrote:
> 
> Hi all,
> 
> I've been able to set up a local ArchivesSpace test instance and am diving into the treasury of available plugins. On top of my list was the as_history plugin (https://gitlab.gaiaresources.com.au/qsa/as_history).
> 
> In short, I'm wondering what its status is. From a previous exchange in May on this mailing list (http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2023-May/010003.html), I recall how James Bullow added the disclaimer that the public version was tied to the specific context in which it had been developed and probably won't work in other contexts. Yet, installing and browsing records' history works like a charm, only restoring previous versions throws an error. 
> 
> Since most of it seems to work surprisingly well, I'd like to know if it has been developed further and is ready for the "outside world". If so:
> would this mailing list be the place to report bugs, or would the Gitlab issue tracker be the best forum?
> has it been used on a large scale? We're migrating a repo of about 2k resources, 190k archival objects, 69k agents into ArchivesSpace. I know as_history will only start logging the history from that migration onward, but I can imagine the history for such an amount of records would be considerable. Is it feasible to use as_history for this magnitude of data?
> 
> Best,
> 
> Ron
> 
> 
> Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis
> Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving |  Boeken en Letteren
> Minderbroedersstraat 22, 2000 Antwerpen
> Grote Markt 1, 2000 Antwerpen
> gsm +32 0485 02 80 50 | tel. +32 3 222 93 30
> letterenhuis.be <http://www.letterenhuis.be/> | instagram <https://www.instagram.com/letterenhuis/> | facebook <https://www.facebook.com/Letterenhuis>
>  
> Proclaimer
> Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, niet voor u bestemd is, vragen we u vriendelijk om dat te melden aan de afzender. Deze e-mail en de bijlagen zijn namelijk offici?le documenten van de stad Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie bevatten. Als stad nemen we privacy heel serieus en willen we als een goede huisvader waken over de vertrouwelijkheid van documenten. Als u dit bericht per vergissing hebt ontvangen of ergens hebt gevonden, wees dan zo eerlijk om het meteen te verwijderen en het niet verder te verspreiden of te kopi?ren.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231214/2efd8c58/attachment.html>

From Ron.VandenBranden at antwerpen.be  Thu Dec 14 04:24:23 2023
From: Ron.VandenBranden at antwerpen.be (Ron Van den Branden)
Date: Thu, 14 Dec 2023 09:24:23 +0000
Subject: [Archivesspace_Users_Group]
	how	to	add	a	new	locale	to	ArchivesSpace?
In-Reply-To: <BL0PR03MB4292F6FEF2F942C7E67A3C38AB8BA@BL0PR03MB4292.namprd03.prod.outlook.com>
References: <AM9PR02MB6915A0EFA9E9233D27C3C0A48884A@AM9PR02MB6915.eurprd02.prod.outlook.com>
 <BL0PR03MB429285CBD09CD003B28C4F6AAB84A@BL0PR03MB4292.namprd03.prod.outlook.com>
 <AM9PR02MB6915C05D88CFCC135AC8CF138884A@AM9PR02MB6915.eurprd02.prod.outlook.com>
 <BL0PR03MB429277DEAE0184082B3D4974AB84A@BL0PR03MB4292.namprd03.prod.outlook.com>
 <AM9PR02MB6915C693049E3712B7F54CE48884A@AM9PR02MB6915.eurprd02.prod.outlook.com>
 <BL0PR03MB42928B8DD87506A258957A24AB84A@BL0PR03MB4292.namprd03.prod.outlook.com>
 <BL0PR03MB42924E671F6C97F4EA8ADFF6AB84A@BL0PR03MB4292.namprd03.prod.outlook.com>
 <BL0PR03MB4292AEDA561A7B08A36DA3E8AB8BA@BL0PR03MB4292.namprd03.prod.outlook.com>
 <BL0PR03MB4292F6FEF2F942C7E67A3C38AB8BA@BL0PR03MB4292.namprd03.prod.outlook.com>
Message-ID: <AM9PR02MB691585CE7A431A50E71AF799888CA@AM9PR02MB6915.eurprd02.prod.outlook.com>

Without wanting to steal Joshua's thunder, the plugin he promptly created is working fine in its current state:

  *
allowing one to specify a custom locale
  *
providing a fallback to a default locale for labels missing in that custom locale

It's dead easy to install, and all nicely documented at https://github.com/dartmouth-dltg/aspace_custom_localizations/, I can't thank you enough, Joshua!

We'll start using this in our system, with Dutch translations for the back-end, front-end, and report sections. The public translation file doesn't look too big, so it should be within reach to translate that as well.

I'm glad the plugin provides a stable way to deploy these custom locales without hacks. This makes it much easier to share them with other parties interested in preparing a complete Dutch translation for future contribution to the ASpace code base. To anyone interested in the Dutch user community: please get in touch!

Best,

Ron

________________________________
Van: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> namens Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Verzonden: donderdag 7 december 2023 19:27
Aan: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Onderwerp: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

U ontvangt niet vaak e-mail van joshua.d.shaw at dartmouth.edu. Meer informatie over waarom dit belangrijk is<https://aka.ms/LearnAboutSenderIdentification>

WAARSCHUWING: DIT IS EEN EXTERNE MAIL

Deze mail komt van buiten onze organisatie. Kijk eerst of je het mailadres en de afzender herkent en/of vertrouwt. Doe dat voor je bijlagen opent of links aanklikt. Zo houden we onze organisatie veiliger voor phishing.

I'm working with Ron to resolve a couple of issues with the plugin and will report back when those are sorted.

jds

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Sent: Thursday, December 7, 2023 8:29 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

Because I was curious, I tested this out and created a small plugin that supports this feature: https://github.com/dartmouth-dltg/aspace_custom_localizations

I tested this against 3.4.1, but I believe it will work with most any version of ArchivesSpace.

Hopefully the ReadMe is self explanatory, but let me know if things are unclear.

jds
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Sent: Wednesday, December 6, 2023 4:03 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

The other way to do this (a bit hacky) is to expand the common.jar file in /lib, make your edits to the relevant I18n file (common/aspace_i18n.rb), and then recompress the jar file.

This works for any edits you need to core, but its hacky because its not really a sustainable way to do things since you need to edit the same file for every? update to the core code.

jds


________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Sent: Wednesday, December 6, 2023 1:13 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

One thing you might try is initializing the AppConfig[:locale] setting  in the plugin itself, since it may be an order of operations issue where the main config loads first which attempts to initialize an unknown language (because the plugin hasn't loaded yet).

jds


________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Ron Van den Branden <Ron.VandenBranden at antwerpen.be>
Sent: Wednesday, December 6, 2023 12:00 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

Hi Joshua,

Thanks again for your detailed steps! Although a first attempt didn't work (startup keeps choking on the original languages list), I'm sure we'll get there, with more time. Thanks for pointing me in the good direction: overriding the language list via plugin initialization. I'll definitely check out those other plugins for inspiration.

Best,

Ron


________________________________
Van: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> namens Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Verzonden: woensdag 6 december 2023 17:21
Aan: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Onderwerp: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

U ontvangt niet vaak e-mail van joshua.d.shaw at dartmouth.edu. Meer informatie over waarom dit belangrijk is<https://aka.ms/LearnAboutSenderIdentification>

WAARSCHUWING: DIT IS EEN EXTERNE MAIL

Deze mail komt van buiten onze organisatie. Kijk eerst of je het mailadres en de afzender herkent en/of vertrouwt. Doe dat voor je bijlagen opent of links aanklikt. Zo houden we onze organisatie veiliger voor phishing.

Hey Ron

Here's the way I'd do this.


  1.  Create a new directory in the plugin folder in your ArchivesSpace directory. Call it something like aspace_custom_locatizations (or whatever you want)
  2.  In that new directory, create two new directories: backend and frontend
  3.  In the backend directory, add a file called plugin_init.rb. Put the contents of the monkey patch in that file
  4.  In the frontend directory, add a file tree that mimics the locales directory in the core code:
     *   locales/
     *   locales/enums
  5.  Add your new dutch locales files to those two locations. Name them nl.yml
  6.  In your config file, add your plugin name (the directory name in step 1) to the list of plugins that are active: AppConfig[:plugins] is the key you want to edit.

Since I haven't tested this, there may be some gotchas I'm not thinking about as far as the monkeypatch and where the locales list may also be referenced, but this is the approach I'd take.

There's more info on that tech docs page and there are a bunch of examples to be found on the Awesome ArchivesSpace repo (https://github.com/archivesspace/awesome-archivesspace) and Hudson Molonglo's repos (https://github.com/hudmol) and https://gitlab.gaiaresources.com.au/explor<https://gitlab.gaiaresources.com.au/explore>

jds


________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Ron Van den Branden <Ron.VandenBranden at antwerpen.be>
Sent: Wednesday, December 6, 2023 11:01 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

Hi Joshua,

Ok, thanks for that pointer! The point is that we couldn't find that common/aspace_i18n.rb file in the ArchivesSpace distribution code. Or are you suggesting to add it in a plugin? If so, would you mind guiding me a bit more?

I don't think we've succeeded in building from source (I'm on Windows, so I'm probably at a loss for local testing, I recall some Ruby build incompatibilities).

Best,

Ron

________________________________
Van: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> namens Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Verzonden: woensdag 6 december 2023 16:44
Aan: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Onderwerp: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

U ontvangt niet vaak e-mail van joshua.d.shaw at dartmouth.edu. Meer informatie over waarom dit belangrijk is<https://aka.ms/LearnAboutSenderIdentification>

WAARSCHUWING: DIT IS EEN EXTERNE MAIL

Deze mail komt van buiten onze organisatie. Kijk eerst of je het mailadres en de afzender herkent en/of vertrouwt. Doe dat voor je bijlagen opent of links aanklikt. Zo houden we onze organisatie veiliger voor phishing.

Hey Ron

In addition to what Christine lists....

Off the top of my head (so take with a grain of salt since I haven't actually tested this!)...

In a plugin init (probably a backend plugin_init), monkey patch the self.supported_locales method in common/aspace_i18n.rb. Maybe something like

module I18n
def self.supported_locales
??????enhanced_locales = LOCALES

??????# map I18n language code => ArchivesSpace enumerations:language_iso639_2 code
??????# enumerations iso codes found in common/locales/enums
??????enhanced_locales['nl'] = 'dut'

??????enhanced_locales
end
end

Then you could add your new dutch locale file nl.yml within that same plugin.

OR

You could grab the code tree from github, patch it locally and build your patched application.

Both approaches have their own set of headaches as far as maintenance.

To contribute and other tech docs: https://archivesspace.github.io/tech-docs/readme_develop.html

Hope that helps!
Joshua



________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Ron Van den Branden <Ron.VandenBranden at antwerpen.be>
Sent: Wednesday, December 6, 2023 9:51 AM
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

Hi all,
We're in the process of customizing the ArchivesSpace (3.4.1) staff interface for use in a Dutch-speaking context. We would like to translate the back-end user interface to Dutch. So far, in order to gain speed, we've resorted to tweaking the en.yml localization files with Dutch labels. In the longer run, hijacking "English" for another language feels like a hack, though.
The documentation for "customizing text" at https://archivesspace.github.io/tech-docs/customization/locales.html  does mention where strings can be customized in current locales, but not how new locales can be added. Simply adding new locale files for new languages, with according names and language codes, at the right locations doesn't seem to do the trick:

  *   either the language is not being offered in the list of available languages
  *
when additionally the new language is specified explicitly in the config/config.rb file as AppConfig[:locale] = :nl , this yields following error at startup:

JSONModel::ValidationException: #<:ValidationException: {:errors=>{"defaults/locale"=>["Invalid value 'nl'.  Must be one of: en, fr, de, ja, es"]}}>

                      validate at uri:classloader:/jsonmodel_type.rb:385

            with_validator_for at uri:classloader:/validator_cache.rb:41

...so there must be more to adding a new locale. Yet, we can't find where in the ArchivesSpace distribution code such a list of default locales can be found or edited.
We did find the file in the ArchivesSpace source tree at https://github.com/archivesspace/archivesspace/blob/master/common/aspace_i18n.rb#L28 which defines above list of locales This file can't be found in the distribution code, however, so it's not clear how it relates to the distribution code. The commit history also shows commits from the Weblate project at https://hosted.weblate.org/projects/archivesspace-interfaces/#languages, which contains additional languages Portuguese and Italian.
This leads to following questions:

  *   what's the mechanism for adding a new locale to an ArchivesSpace instance?
  *   if our translations would reach a stage of being of broader interest, what would be the procedure for contributing them?

Kind regards,
Ron


Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis

Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving |  Boeken en Letteren

Minderbroedersstraat 22, 2000 Antwerpen

Grote Markt 1, 2000 Antwerpen

gsm +32 0485 02 80 50 | tel. +32 3 222 93 30

letterenhuis.be<http://www.letterenhuis.be/> | instagram<https://www.instagram.com/letterenhuis/> | facebook<https://www.facebook.com/Letterenhuis>



Proclaimer

Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, niet voor u bestemd is, vragen we u vriendelijk om dat te melden aan de afzender. Deze e-mail en de bijlagen zijn namelijk offici?le documenten van de stad Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie bevatten. Als stad nemen we privacy heel serieus en willen we als een goede huisvader waken over de vertrouwelijkheid van documenten. Als u dit bericht per vergissing hebt ontvangen of ergens hebt gevonden, wees dan zo eerlijk om het meteen te verwijderen en het niet verder te verspreiden of te kopi?ren.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231214/c485fbd8/attachment.html>

From Joshua.D.Shaw at dartmouth.edu  Thu Dec 14 06:57:13 2023
From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw)
Date: Thu, 14 Dec 2023 11:57:13 +0000
Subject: [Archivesspace_Users_Group]
	how	to	add	a	new	locale	to	ArchivesSpace?
In-Reply-To: <AM9PR02MB691585CE7A431A50E71AF799888CA@AM9PR02MB6915.eurprd02.prod.outlook.com>
References: <AM9PR02MB6915A0EFA9E9233D27C3C0A48884A@AM9PR02MB6915.eurprd02.prod.outlook.com>
 <BL0PR03MB429285CBD09CD003B28C4F6AAB84A@BL0PR03MB4292.namprd03.prod.outlook.com>
 <AM9PR02MB6915C05D88CFCC135AC8CF138884A@AM9PR02MB6915.eurprd02.prod.outlook.com>
 <BL0PR03MB429277DEAE0184082B3D4974AB84A@BL0PR03MB4292.namprd03.prod.outlook.com>
 <AM9PR02MB6915C693049E3712B7F54CE48884A@AM9PR02MB6915.eurprd02.prod.outlook.com>
 <BL0PR03MB42928B8DD87506A258957A24AB84A@BL0PR03MB4292.namprd03.prod.outlook.com>
 <BL0PR03MB42924E671F6C97F4EA8ADFF6AB84A@BL0PR03MB4292.namprd03.prod.outlook.com>
 <BL0PR03MB4292AEDA561A7B08A36DA3E8AB8BA@BL0PR03MB4292.namprd03.prod.outlook.com>
 <BL0PR03MB4292F6FEF2F942C7E67A3C38AB8BA@BL0PR03MB4292.namprd03.prod.outlook.com>
 <AM9PR02MB691585CE7A431A50E71AF799888CA@AM9PR02MB6915.eurprd02.prod.outlook.com>
Message-ID: <BYAPR03MB42939275F2ABF9A0834F9F21AB8CA@BYAPR03MB4293.namprd03.prod.outlook.com>

Just wanted to chime in to say this was an interesting challenge involving some pieces of ArchivesSpace that I hadn't poked around in as much. Having someone to test the changes was super helpful, so thanks to Ron for that side of things!

I'd also like to emphasize that the main goal for anyone using the plugin will hopefully be eventual contribution of their custom localizations to core. The more languages represented in core, the better!

Please send any bug reports or thoughts for enhancements my way.

Joshua


________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Ron Van den Branden <Ron.VandenBranden at antwerpen.be>
Sent: Thursday, December 14, 2023 4:24 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

Without wanting to steal Joshua's thunder, the plugin he promptly created is working fine in its current state:

  *
allowing one to specify a custom locale
  *
providing a fallback to a default locale for labels missing in that custom locale

It's dead easy to install, and all nicely documented at https://github.com/dartmouth-dltg/aspace_custom_localizations/, I can't thank you enough, Joshua!

We'll start using this in our system, with Dutch translations for the back-end, front-end, and report sections. The public translation file doesn't look too big, so it should be within reach to translate that as well.

I'm glad the plugin provides a stable way to deploy these custom locales without hacks. This makes it much easier to share them with other parties interested in preparing a complete Dutch translation for future contribution to the ASpace code base. To anyone interested in the Dutch user community: please get in touch!

Best,

Ron

________________________________
Van: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> namens Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Verzonden: donderdag 7 december 2023 19:27
Aan: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Onderwerp: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

U ontvangt niet vaak e-mail van joshua.d.shaw at dartmouth.edu. Meer informatie over waarom dit belangrijk is<https://aka.ms/LearnAboutSenderIdentification>

WAARSCHUWING: DIT IS EEN EXTERNE MAIL

Deze mail komt van buiten onze organisatie. Kijk eerst of je het mailadres en de afzender herkent en/of vertrouwt. Doe dat voor je bijlagen opent of links aanklikt. Zo houden we onze organisatie veiliger voor phishing.

I'm working with Ron to resolve a couple of issues with the plugin and will report back when those are sorted.

jds

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Sent: Thursday, December 7, 2023 8:29 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

Because I was curious, I tested this out and created a small plugin that supports this feature: https://github.com/dartmouth-dltg/aspace_custom_localizations

I tested this against 3.4.1, but I believe it will work with most any version of ArchivesSpace.

Hopefully the ReadMe is self explanatory, but let me know if things are unclear.

jds
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Sent: Wednesday, December 6, 2023 4:03 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

The other way to do this (a bit hacky) is to expand the common.jar file in /lib, make your edits to the relevant I18n file (common/aspace_i18n.rb), and then recompress the jar file.

This works for any edits you need to core, but its hacky because its not really a sustainable way to do things since you need to edit the same file for every? update to the core code.

jds


________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Sent: Wednesday, December 6, 2023 1:13 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

One thing you might try is initializing the AppConfig[:locale] setting  in the plugin itself, since it may be an order of operations issue where the main config loads first which attempts to initialize an unknown language (because the plugin hasn't loaded yet).

jds


________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Ron Van den Branden <Ron.VandenBranden at antwerpen.be>
Sent: Wednesday, December 6, 2023 12:00 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

Hi Joshua,

Thanks again for your detailed steps! Although a first attempt didn't work (startup keeps choking on the original languages list), I'm sure we'll get there, with more time. Thanks for pointing me in the good direction: overriding the language list via plugin initialization. I'll definitely check out those other plugins for inspiration.

Best,

Ron


________________________________
Van: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> namens Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Verzonden: woensdag 6 december 2023 17:21
Aan: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Onderwerp: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

U ontvangt niet vaak e-mail van joshua.d.shaw at dartmouth.edu. Meer informatie over waarom dit belangrijk is<https://aka.ms/LearnAboutSenderIdentification>

WAARSCHUWING: DIT IS EEN EXTERNE MAIL

Deze mail komt van buiten onze organisatie. Kijk eerst of je het mailadres en de afzender herkent en/of vertrouwt. Doe dat voor je bijlagen opent of links aanklikt. Zo houden we onze organisatie veiliger voor phishing.

Hey Ron

Here's the way I'd do this.


  1.  Create a new directory in the plugin folder in your ArchivesSpace directory. Call it something like aspace_custom_locatizations (or whatever you want)
  2.  In that new directory, create two new directories: backend and frontend
  3.  In the backend directory, add a file called plugin_init.rb. Put the contents of the monkey patch in that file
  4.  In the frontend directory, add a file tree that mimics the locales directory in the core code:
     *   locales/
     *   locales/enums
  5.  Add your new dutch locales files to those two locations. Name them nl.yml
  6.  In your config file, add your plugin name (the directory name in step 1) to the list of plugins that are active: AppConfig[:plugins] is the key you want to edit.

Since I haven't tested this, there may be some gotchas I'm not thinking about as far as the monkeypatch and where the locales list may also be referenced, but this is the approach I'd take.

There's more info on that tech docs page and there are a bunch of examples to be found on the Awesome ArchivesSpace repo (https://github.com/archivesspace/awesome-archivesspace) and Hudson Molonglo's repos (https://github.com/hudmol) and https://gitlab.gaiaresources.com.au/explor<https://gitlab.gaiaresources.com.au/explore>

jds


________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Ron Van den Branden <Ron.VandenBranden at antwerpen.be>
Sent: Wednesday, December 6, 2023 11:01 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

Hi Joshua,

Ok, thanks for that pointer! The point is that we couldn't find that common/aspace_i18n.rb file in the ArchivesSpace distribution code. Or are you suggesting to add it in a plugin? If so, would you mind guiding me a bit more?

I don't think we've succeeded in building from source (I'm on Windows, so I'm probably at a loss for local testing, I recall some Ruby build incompatibilities).

Best,

Ron

________________________________
Van: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> namens Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Verzonden: woensdag 6 december 2023 16:44
Aan: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Onderwerp: Re: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

U ontvangt niet vaak e-mail van joshua.d.shaw at dartmouth.edu. Meer informatie over waarom dit belangrijk is<https://aka.ms/LearnAboutSenderIdentification>

WAARSCHUWING: DIT IS EEN EXTERNE MAIL

Deze mail komt van buiten onze organisatie. Kijk eerst of je het mailadres en de afzender herkent en/of vertrouwt. Doe dat voor je bijlagen opent of links aanklikt. Zo houden we onze organisatie veiliger voor phishing.

Hey Ron

In addition to what Christine lists....

Off the top of my head (so take with a grain of salt since I haven't actually tested this!)...

In a plugin init (probably a backend plugin_init), monkey patch the self.supported_locales method in common/aspace_i18n.rb. Maybe something like

module I18n
def self.supported_locales
??????enhanced_locales = LOCALES

??????# map I18n language code => ArchivesSpace enumerations:language_iso639_2 code
??????# enumerations iso codes found in common/locales/enums
??????enhanced_locales['nl'] = 'dut'

??????enhanced_locales
end
end

Then you could add your new dutch locale file nl.yml within that same plugin.

OR

You could grab the code tree from github, patch it locally and build your patched application.

Both approaches have their own set of headaches as far as maintenance.

To contribute and other tech docs: https://archivesspace.github.io/tech-docs/readme_develop.html

Hope that helps!
Joshua



________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Ron Van den Branden <Ron.VandenBranden at antwerpen.be>
Sent: Wednesday, December 6, 2023 9:51 AM
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] how to add a new locale to ArchivesSpace?

Hi all,
We're in the process of customizing the ArchivesSpace (3.4.1) staff interface for use in a Dutch-speaking context. We would like to translate the back-end user interface to Dutch. So far, in order to gain speed, we've resorted to tweaking the en.yml localization files with Dutch labels. In the longer run, hijacking "English" for another language feels like a hack, though.
The documentation for "customizing text" at https://archivesspace.github.io/tech-docs/customization/locales.html  does mention where strings can be customized in current locales, but not how new locales can be added. Simply adding new locale files for new languages, with according names and language codes, at the right locations doesn't seem to do the trick:

  *   either the language is not being offered in the list of available languages
  *
when additionally the new language is specified explicitly in the config/config.rb file as AppConfig[:locale] = :nl , this yields following error at startup:

JSONModel::ValidationException: #<:ValidationException: {:errors=>{"defaults/locale"=>["Invalid value 'nl'.  Must be one of: en, fr, de, ja, es"]}}>

                      validate at uri:classloader:/jsonmodel_type.rb:385

            with_validator_for at uri:classloader:/validator_cache.rb:41

...so there must be more to adding a new locale. Yet, we can't find where in the ArchivesSpace distribution code such a list of default locales can be found or edited.
We did find the file in the ArchivesSpace source tree at https://github.com/archivesspace/archivesspace/blob/master/common/aspace_i18n.rb#L28 which defines above list of locales This file can't be found in the distribution code, however, so it's not clear how it relates to the distribution code. The commit history also shows commits from the Weblate project at https://hosted.weblate.org/projects/archivesspace-interfaces/#languages, which contains additional languages Portuguese and Italian.
This leads to following questions:

  *   what's the mechanism for adding a new locale to an ArchivesSpace instance?
  *   if our translations would reach a stage of being of broader interest, what would be the procedure for contributing them?

Kind regards,
Ron


Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis

Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving |  Boeken en Letteren

Minderbroedersstraat 22, 2000 Antwerpen

Grote Markt 1, 2000 Antwerpen

gsm +32 0485 02 80 50 | tel. +32 3 222 93 30

letterenhuis.be<http://www.letterenhuis.be/> | instagram<https://www.instagram.com/letterenhuis/> | facebook<https://www.facebook.com/Letterenhuis>



Proclaimer

Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, niet voor u bestemd is, vragen we u vriendelijk om dat te melden aan de afzender. Deze e-mail en de bijlagen zijn namelijk offici?le documenten van de stad Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie bevatten. Als stad nemen we privacy heel serieus en willen we als een goede huisvader waken over de vertrouwelijkheid van documenten. Als u dit bericht per vergissing hebt ontvangen of ergens hebt gevonden, wees dan zo eerlijk om het meteen te verwijderen en het niet verder te verspreiden of te kopi?ren.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231214/76f62b3e/attachment.html>

From benefiea at gvsu.edu  Thu Dec 14 10:26:38 2023
From: benefiea at gvsu.edu (Annie Benefiel)
Date: Thu, 14 Dec 2023 15:26:38 +0000
Subject: [Archivesspace_Users_Group] Call for Volunteers: Code of Conduct
	Review Task Force
Message-ID: <BN0PR16MB4511953D4BF3F26256429A83B08CA@BN0PR16MB4511.namprd16.prod.outlook.com>

The ArchivesSpace Governance Board seeks 1-3 community volunteers to serve on the ArchivesSpace Code of Conduct Review Task Force.

In April 2023, the content of a presentation at the ArchivesSpace Virtual Member Forum received complaints that warranted the first application of our community Code of Conduct. As a follow up, the Governance Board has charged a task force to review the Code of Conduct to improve its guidelines and procedures.

The review will address the following:

  *   Review the response procedures and timeline to ensure opportunities for dialogue and understanding,
  *   Review the possible need for, and impact of, complainant anonymity.
  *   Develop guidelines for invoking the Code of Conduct, and creating clarity on steps to take if complaints are received or concerns are raised outside of the normal reporting procedures.

Next steps for the community and program team to consider which may include developing guidelines for discussions of harmful archival material within the ArchivesSpace community.

Task Force Composition:

The community volunteers will join three members of ArchivesSpace's governance groups: 1 member of the Board (who will Chair the task force), and 2 members of the ArchivesSpace User Advisory Council's Member Engagement Sub-team.

The Task Force may also engage a DEI Facilitator of Consultant to help guide its work and provide training.

Eligibility:

Volunteers should be presently employed by an ArchivesSpace member institution (please refer to the categorized member list at: <http://www.archivesspace.org/members> http://archivesspace.org/community/whos-using-archivesspace/).

We encourage individuals with experience and/or interest in code of conduct development or review to volunteer. We especially encourage Black, Indigenous, and People of Color, and others currently less represented in our governance groups to consider joining us in this important endeavor.

The anticipated time commitment for task force members will be 1-3 hours per month. The term of service will be approximately January-June 2024.

Please fill out this form including your name, contact information, and a brief statement of interest and motivation to join the task force by January 9th, 2024. https://forms.gle/uvbn6gv34P2bFTDJ8

Annie Benefiel
Chair, Code of Conduct Review Task Force
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231214/c08a9c5b/attachment.html>

From christine.dibella at lyrasis.org  Wed Dec 20 09:46:08 2023
From: christine.dibella at lyrasis.org (Christine Di Bella)
Date: Wed, 20 Dec 2023 14:46:08 +0000
Subject: [Archivesspace_Users_Group] upcoming listserv change to Google
	Groups
Message-ID: <MN2PR22MB188720F8306C30E37E9BB426F196A@MN2PR22MB1887.namprd22.prod.outlook.com>

Hello ArchivesSpace members,



As noted in the last monthly update, Lyrasis, the organizational home for ArchivesSpace, is transitioning away from the Mailman platform for listservs to Google Groups in the near future. The ArchivesSpace member listservs, including the Users Group, will become Google Groups with email delivery after the transition. Right now the move is planned to occur between December 26 and January 1, but the work of setting up the groups and migrating accounts to some of the new listservs in preparation for the transition has already begun. All accounts subscribed to our member listservs at the time of the transition will be moved to the new platform, with equivalent settings to what users have currently.



You do not need to set up a Google account with the address currently subscribed to ArchivesSpace listservs if you only wish to send and receive list messages via email. If you want to use the web functionalities of Google Groups you will need to make sure the address you use with the listservs is associated with a Google account. Most listserv names will remain the same, but the new domain for the listservs will be lyralists.org rather than lyralists.lyrasis.org. You may want to make sure that the new listserv addresses are added to your address book or otherwise set not to be caught by any spam filters you have in place. If you have opted out from Google Groups in general, you will need to change that setting to get listserv mail.


For now the archives of our listservs through 2023 will be maintained on the current platform, and will stay there for at least a year. Some details of the transition are still to be determined, including how listserv archives will be available after the planned one-year period. We know that the archives of the Users Group listserv, in particular, are an important source of information for the community.


We are hopeful that the new platform will be useful in providing easier ways to post and access content, as well as easier administration of the lists overall. If you have any questions about this change, please feel free to get in touch with us at ArchivesSpaceHome at lyrasis.org<mailto:ArchivesSpaceHome at lyrasis.org>.

Christine

Christine Di Bella
ArchivesSpace Senior Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>

[cid:image001.jpg at 01DA3324.72F02170]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231220/56ef4392/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 56099 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231220/56ef4392/attachment.jpg>

From bailey-grace.harrell at lyrasis.org  Fri Dec 22 10:09:57 2023
From: bailey-grace.harrell at lyrasis.org (Bailey-Grace Harrell)
Date: Fri, 22 Dec 2023 15:09:57 +0000
Subject: [Archivesspace_Users_Group] ArchivesSpace Update - December 2023
Message-ID: <CYYPR22MB4158FC75450336365C2C0F06C694A@CYYPR22MB4158.namprd22.prod.outlook.com>

  [cid:image001.jpg at 01DA34BE.91695180]


ArchivesSpace Update ? December 2023


Upcoming Schedule at a Glance:

  *   December 25 - January 1 | ArchivesSpace office closed
  *   January 9, 2024 | Deadline to apply for Code of Conduct Task Force
  *   March 26-27, 2024 | Virtual Member Forum



Development

We continue to gather up development and testing work for the next release. As the end of the calendar year is fast approaching, it looks like we will not have time to complete everything that needs to be done to put out another release in 2023. You can expect a new release early in 2024 instead. New development is always up on our test server at https://test.archivesspace.org/staff/.


Transition for ArchivesSpace Listservs

Lyrasis, the organizational home for ArchivesSpace, is planning to transition away from the Mailman platform for listservs to Google Groups in the near future. The ArchivesSpace member listservs, including the Users Group, will become Google Groups with email delivery after the transition. Right now the move is planned to occur between December 26 and January 1. All accounts subscribed to our member listservs at the time of the transition will be moved to the new platform, with equivalent settings to what users have currently.


For now the archives of our listservs will be maintained on the current platform, and will stay there for at least a year. Some details of the transition are still to be determined, including how listserv archives will be available after the planned one year period when they will remain on the current platform. We know that the archives of the Users Group listserv, in particular, are an important source of information for the community and are working to ensure that access to them remains consistent.


If you have any questions about this change, please feel free to get in touch with us at ArchivesSpaceHome at lyrasis.org<mailto:ArchivesSpaceHome at lyrasis.org>.


Call for Volunteers: Code of Conduct Review Task Force

[Posted on behalf of the Code of Conduct Review Task Force]

We are seeking 1-3 volunteers to serve on a task force to review the ArchivesSpace Community Code of Conduct from January to June 2024. Individuals with experience and/or interest in code of conduct development or review are strongly encouraged to volunteer. We especially encourage Black, Indigenous, and People of Color, and others currently less represented in our governance groups to consider joining us in this important endeavor. Please indicate your interest by filling out this form by January 9, 2024: https://forms.gle/uvbn6gv34P2bFTDJ8

ArchivesSpace Virtual Member Forum 2024 - Save the Date

Mark your calendars for our 2024 Virtual Member Forum! Taking place March 26-27, 2024, our Virtual Member Forum will be a two-day event spanning a variety of time zones and ArchivesSpace experience levels.

More information will be provided soon about how to propose a topic or presentation.  Registration will open closer to the event date.  For now, be sure to save the date on your calendar.  We look forward to ?seeing? many of you there.



Live Demonstration: Overview of the ArchivesSpace Application and Membership Benefits

Thank you to everyone who attended our demonstration of ArchivesSpace on December 6.  A recording of that session is now available on our YouTube channel at https://www.youtube.com/watch?v=1vpSKwF3Lf4&feature=youtu.be



For more information about this demo, ArchivesSpace, and ArchivesSpace membership, email ArchivesSpaceHome at lyrasis.org<mailto:ArchivesSpaceHome at lyrasis.org>.



ArchivesSpace Holiday Hours

Our office will be closed from December 25 to January 1. Normal office hours will resume on January 2nd. We wish you all warm and happy holidays!


Membership Update

We are excited to welcome our newest members to our community! Some of our new members since November 30th include:

  *   Albion College | Albion, MI
  *   American Academy of Pediatrics | Itasca, IL
  *   The National WWII Museum | New Orleans, LA

As of December 22nd, we have 479 General members, 20 Educational Program members, 3 Registered Service Providers, and 1 Consortium Provider.

Thank you to our current ArchivesSpace members<https://archivesspace.org/community/whos-using-archivesspace> for your contribution to the development and sustainability of the ArchivesSpace application.  ArchivesSpace has a membership model<https://archivesspace.org/community/why-become-a-member> to support the continued development of the application and user community and ArchivesSpace members are eligible for a variety of benefits<https://archivesspace.org/community/member-benefits>.  If you are interested in ArchivesSpace membership<https://archivesspace.org/community/making_a_case_for_membership> for your organization, email us at ArchivesSpaceHome at lyrasis.org<mailto:ArchivesSpaceHome at lyrasis.org>.

________________________________

ArchivesSpace monthly updates provide news about ArchivesSpace community and program activities and are sent to our member listservs, the ArchivesSpace Google Group, and SAA?s Collection Management Section listserv, as well as being posted on the ArchivesSpace website. Please feel free to share this update with people you know who have an interest in ArchivesSpace but may not be on one of these lists.



Bailey-Grace Harrell
ArchivesSpace Program Assistant
Bailey-grace.harrell at lyrasis.com<mailto:Bailey-grace.harrell at lyrasis.com>

[signature_76019080]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231222/9400e2da/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 49178 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231222/9400e2da/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 224996 bytes
Desc: image002.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231222/9400e2da/attachment-0001.png>