[Archivesspace_Users_Group] Editing display columns for Collection Management in AS

[Suszczynski, Jeffrey]

Hello, everyone -

We are trying to modify the columns that display in Collection Management 
(Browse ==> Collection Management ... We've looked in various places within the 
web admin interface, as well as the most often-edited configuration files on 
our AS server, but thus far have not been able to find where these columns are 
set.  For reference, here is a screen shot from our web admin interface:

[cid:image003.jpg@01D64599.4674C960]

Does anyone know where we might make changes to this display?  Hopefully it's 
something simple that we overlooked - thanks in advance!

Jeff

Jeff Suszczynski
Web Developer, River Campus Libraries
University of Rochester


___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] Take a break with ArchivesSpace on Friday cancelled this week

[Jessica Crouch]

Dear ArchivesSpace Users,



LYRASIS will be observing Juneteenth tomorrow and staff will not be available 
for our standing Friday afternoon break.  We will resume our Friday breaks with 
ArchivesSpace next Friday, June 26th.



Thank you to everyone who joined us last week for a great chat.  We look 
forward to seeing you again next Friday.


Best,
Jessica

Jessica Dowd Crouch
Community Engagement Coordinator for ArchivesSpace
jessica.cro...@lyrasis.org
[page1image482511520]

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] Partially deleted repository

[Sharp, Jennifer]

Hi all,

Last year when we were considering joining ArchivesSpace, our IT department 
created a test repository for me. When we joined, they created our "real" 
repository, which I am still using. When I go to Manage Repositories (signed in 
as Admin), the test repository is still listed, but I am unable to view or edit 
it. I get a Record Not Found message. There is one, incomplete, finding aid in 
the test repository, that is still accessible via the public interface. Is 
there a way I can gain access to the test repository, or at least get rid of 
the incomplete finding aid?

Thanks,
Jennifer

---
Jennifer Sharp, MSI
Archivist, Hartford History Center
Hartford Public Library
jsh...@hplct.org
(o: 860.695.6332 Wed. only, currently)
c: 860.929.6915

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Top container ranges

[Hilton, Adrien]

Hi Dawne,

I believe Yale created a script to break out container ranges: 
https://github.com/YaleArchivesSpace/xslt-files/blob/master/EAD_expand_top_container_ranges_prior_to_import.xsl

Best wishes,
Adrien

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Mayo, 
Dave
Sent: Thursday, June 18, 2020 9:23 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Top container ranges

So, with the caveat that we put a lot of resources (a bunch of archivists’ 
time, a full year of a full time developer (me!)), we had very solid results; I 
think remediating issues prior to import is almost always worth the expense of 
significant effort, particularly over a large corpus.

My main advice would be to be very, very careful about changes – version your 
EADs, compare before and after scripts run, and in general be very systematic 
about how you find, report, and correct changes.

I don’t know if you’ve seen it, but Kate Bowers and I did a write-up of what we 
did during our migration – it has links to a number of open source tools I 
wrote for doing this kind of work.  They’re a bit involved to get running, but 
they definitely work at basically any scale out there, and I’m happy to help 
people get started with them.  
https://journal.code4lib.org/articles/12239

--
Dave Mayo (he/him)
Senior Digital Library Software Engineer
Harvard University > HUIT > LTS

From: 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of "Lucas, Dawne Howard" 
mailto:dawne_lu...@unc.edu>>
Reply-To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Date: Thursday, June 18, 2020 at 9:12 AM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Top container ranges

Thanks, Dave.  I guess I should have specified that changing the EAD isn’t a 
viable solution for us unless it’s automated. We do not plan to edit individual 
finding aids manually except in cases where the ranges aren’t regular.

If you’ve done this at Harvard, have there been any drawbacks? Anything we 
should be looking to avoid?

Thanks again,

Dawne


From: Mayo, Dave
Sent: Thursday, June 18, 2020 9:04 AM
To: Archivesspace Users 
Group
Subject: Re: [Archivesspace_Users_Group] Top container ranges

The two options I see here are essentially:

1. Change the EAD
2. Change the containers after they’re ingested.

Of the two, changing the EAD seems _easier_ to me; if you wouldn’t mind going 
more into why that’s not a viable solution for you, it might help us provide 
better advice?

Either way, at 7000 finding aids, the solution would basically need to be 
automated – if your box ranges are very regular (i.e. only single number or 
range, no “3,4,7-10” or similar), it wouldn’t be too difficult – split the 
range on ‘-‘, generate list of numbers, replace container with multiple 
containers.
--
Dave Mayo (he/him)
Senior Digital Library Software Engineer
Harvard University > HUIT > LTS

From: 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of "Lucas, Dawne Howard" 
mailto:dawne_lu...@unc.edu>>
Reply-To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Date: Thursday, June 18, 2020 at 8:13 AM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Top container ranges


Hi all,



We are formulating a plan to import our 7000+ EAD finding aids into 
ArchivesSpace and are wondering how other institutions have handled top 
container ranges.



For example, we have finding aids coded like this:



3-4Photographs



This imports into ASpace just fine (yay!), but of course also creates a top 
container for Box 3-4 instead of Box 3 and Box 4 (boo!). We assume this will be 
an issue later when we integrate with Aeon.



The most obvious solution to this problem appears to be to change the encoding 
to:



3Photographs



4 
Photographs



For several reasons, this is not a viable solution for us. Have other 
institutions figured out a way to deal with this issue that does not include 
editing the EAD in individual finding aids?

Thanks for your help,

Dawne

--
Dawne Howard Lucas (she/her/hers)
Technical Services Archivist

Wilson Special Collections Library
200 South Road, CB #3926
Chapel Hill, NC 27515
The University of North Carolina at Chapel Hill
P  919-966-1776   E  dawne_lu...@unc.edu

Re: [Archivesspace_Users_Group] Top container ranges

[Bowers, Kate A.]

What Dave said.

From a practical standpoint, you have these options:

1.  Change the EAD pre-migration

2.  Change the data in Aspace

3.  Live with the data like that (your cost of cleaning v living with it 
may vary, but it is worth having the discussion. My repository had some issues 
we decided to live with and some we decided to fix.)

Option 1 works if you have consistency in the choices folks have made in 
finding aids. Unfortunately at Harvard, for some repositories text like “Box 
3-4” referred to a single box with the identifier 3-4, and not to “Box 3 and 
Box 4”. Thus, we could not implement a single script that would work for all 
cases. We were also constrained by time and could not implement scripted 
solutions across sub-sets of our corpus. However…

Individual repositories did implement changes in their own ways. We had very 
few of these “box range” type of finding aids, so I (OK, I know this is a 
really crude, sledgehammer type of method!)

·Got the subset of finding aid that have this issue (granted, this can 
be some task in itself)

·Put them in their own directory

·Used regex find-and-replace (taking great care, of course to do no 
harm by accident) in either my favorite text editor or oXygen to 
find-and-replace all instances of the problem

·Double-checked that they were all still valid

·Spot-checked the results
Your mileage and access to a real programmer for stuff like this may vary.




From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Mayo, 
Dave
Sent: Thursday, June 18, 2020 9:37 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Top container ranges

Also, specifically:


  1.  Using an XML database like eXist-db or BaseX with XPath/XQuery was 
invaluable when doing analysis of issues and of the impact of changes
  2.  One of the tools I wrote, the EAD Checker, is available online: 
https://eadchecker.lib.harvard.edu – it doesn’t catch this specific issue, but 
it does catch a bunch of issues, some of which cause corrupted data rather than 
failure to import.

--
Dave Mayo (he/him)
Senior Digital Library Software Engineer
Harvard University > HUIT > LTS

From: 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of "Mayo, Dave" mailto:dave_m...@harvard.edu>>
Reply-To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Date: Thursday, June 18, 2020 at 9:23 AM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Top container ranges

So, with the caveat that we put a lot of resources (a bunch of archivists’ 
time, a full year of a full time developer (me!)), we had very solid results; I 
think remediating issues prior to import is almost always worth the expense of 
significant effort, particularly over a large corpus.

My main advice would be to be very, very careful about changes – version your 
EADs, compare before and after scripts run, and in general be very systematic 
about how you find, report, and correct changes.

I don’t know if you’ve seen it, but Kate Bowers and I did a write-up of what we 
did during our migration – it has links to a number of open source tools I 
wrote for doing this kind of work.  They’re a bit involved to get running, but 
they definitely work at basically any scale out there, and I’m happy to help 
people get started with them.  
https://journal.code4lib.org/articles/12239

--
Dave Mayo (he/him)
Senior Digital Library Software Engineer
Harvard University > HUIT > LTS

From: 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of "Lucas, Dawne Howard" 
mailto:dawne_lu...@unc.edu>>
Reply-To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Date: Thursday, June 18, 2020 at 9:12 AM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Top container ranges

Thanks, Dave.  I guess I should have specified that changing the EAD isn’t a 
viable solution for us unless it’s automated. We do not plan to edit individual 
finding aids manually except in cases where the ranges aren’t regular.

If you’ve done this at Harvard, have there been any drawbacks? Anything we 
should be looking to avoid?

Thanks again,

Dawne


From: Mayo, Dave
Sent: Thursday, June 18, 2020 9:04 AM
To: Archivesspace Users 
Group
Subject: Re: [Archivesspace_Users_Group] Top container ranges

The two options I see here are essentially:

1. Change the EAD
2. Change the containers after 

Re: [Archivesspace_Users_Group] Top container ranges

[Mayo, Dave]

Also, specifically:


  1.  Using an XML database like eXist-db or BaseX with XPath/XQuery was 
invaluable when doing analysis of issues and of the impact of changes
  2.  One of the tools I wrote, the EAD Checker, is available online: 
https://eadchecker.lib.harvard.edu – it doesn’t catch this specific issue, but 
it does catch a bunch of issues, some of which cause corrupted data rather than 
failure to import.

--
Dave Mayo (he/him)
Senior Digital Library Software Engineer
Harvard University > HUIT > LTS

From:  on behalf of 
"Mayo, Dave" 
Reply-To: Archivesspace Users Group 

Date: Thursday, June 18, 2020 at 9:23 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Top container ranges

So, with the caveat that we put a lot of resources (a bunch of archivists’ 
time, a full year of a full time developer (me!)), we had very solid results; I 
think remediating issues prior to import is almost always worth the expense of 
significant effort, particularly over a large corpus.

My main advice would be to be very, very careful about changes – version your 
EADs, compare before and after scripts run, and in general be very systematic 
about how you find, report, and correct changes.

I don’t know if you’ve seen it, but Kate Bowers and I did a write-up of what we 
did during our migration – it has links to a number of open source tools I 
wrote for doing this kind of work.  They’re a bit involved to get running, but 
they definitely work at basically any scale out there, and I’m happy to help 
people get started with them.  
https://journal.code4lib.org/articles/12239

--
Dave Mayo (he/him)
Senior Digital Library Software Engineer
Harvard University > HUIT > LTS

From:  on behalf of 
"Lucas, Dawne Howard" 
Reply-To: Archivesspace Users Group 

Date: Thursday, June 18, 2020 at 9:12 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Top container ranges

Thanks, Dave.  I guess I should have specified that changing the EAD isn’t a 
viable solution for us unless it’s automated. We do not plan to edit individual 
finding aids manually except in cases where the ranges aren’t regular.

If you’ve done this at Harvard, have there been any drawbacks? Anything we 
should be looking to avoid?

Thanks again,

Dawne


From: Mayo, Dave
Sent: Thursday, June 18, 2020 9:04 AM
To: Archivesspace Users 
Group
Subject: Re: [Archivesspace_Users_Group] Top container ranges

The two options I see here are essentially:

1. Change the EAD
2. Change the containers after they’re ingested.

Of the two, changing the EAD seems _easier_ to me; if you wouldn’t mind going 
more into why that’s not a viable solution for you, it might help us provide 
better advice?

Either way, at 7000 finding aids, the solution would basically need to be 
automated – if your box ranges are very regular (i.e. only single number or 
range, no “3,4,7-10” or similar), it wouldn’t be too difficult – split the 
range on ‘-‘, generate list of numbers, replace container with multiple 
containers.
--
Dave Mayo (he/him)
Senior Digital Library Software Engineer
Harvard University > HUIT > LTS

From:  on behalf of 
"Lucas, Dawne Howard" 
Reply-To: Archivesspace Users Group 

Date: Thursday, June 18, 2020 at 8:13 AM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Top container ranges


Hi all,



We are formulating a plan to import our 7000+ EAD finding aids into 
ArchivesSpace and are wondering how other institutions have handled top 
container ranges.



For example, we have finding aids coded like this:



3-4Photographs



This imports into ASpace just fine (yay!), but of course also creates a top 
container for Box 3-4 instead of Box 3 and Box 4 (boo!). We assume this will be 
an issue later when we integrate with Aeon.



The most obvious solution to this problem appears to be to change the encoding 
to:



3Photographs



4 
Photographs



For several reasons, this is not a viable solution for us. Have other 
institutions figured out a way to deal with this issue that does not include 
editing the EAD in individual finding aids?

Thanks for your help,

Dawne

--
Dawne Howard Lucas (she/her/hers)
Technical Services Archivist

Wilson Special Collections Library
200 South Road, CB #3926
Chapel Hill, NC 27515
The University of North Carolina at Chapel Hill
P  919-966-1776   E  dawne_lu...@unc.edu

Re: [Archivesspace_Users_Group] Top container ranges

[Mayo, Dave]

So, with the caveat that we put a lot of resources (a bunch of archivists’ 
time, a full year of a full time developer (me!)), we had very solid results; I 
think remediating issues prior to import is almost always worth the expense of 
significant effort, particularly over a large corpus.

My main advice would be to be very, very careful about changes – version your 
EADs, compare before and after scripts run, and in general be very systematic 
about how you find, report, and correct changes.

I don’t know if you’ve seen it, but Kate Bowers and I did a write-up of what we 
did during our migration – it has links to a number of open source tools I 
wrote for doing this kind of work.  They’re a bit involved to get running, but 
they definitely work at basically any scale out there, and I’m happy to help 
people get started with them.  https://journal.code4lib.org/articles/12239

--
Dave Mayo (he/him)
Senior Digital Library Software Engineer
Harvard University > HUIT > LTS

From:  on behalf of 
"Lucas, Dawne Howard" 
Reply-To: Archivesspace Users Group 

Date: Thursday, June 18, 2020 at 9:12 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Top container ranges

Thanks, Dave.  I guess I should have specified that changing the EAD isn’t a 
viable solution for us unless it’s automated. We do not plan to edit individual 
finding aids manually except in cases where the ranges aren’t regular.

If you’ve done this at Harvard, have there been any drawbacks? Anything we 
should be looking to avoid?

Thanks again,

Dawne


From: Mayo, Dave
Sent: Thursday, June 18, 2020 9:04 AM
To: Archivesspace Users 
Group
Subject: Re: [Archivesspace_Users_Group] Top container ranges

The two options I see here are essentially:

1. Change the EAD
2. Change the containers after they’re ingested.

Of the two, changing the EAD seems _easier_ to me; if you wouldn’t mind going 
more into why that’s not a viable solution for you, it might help us provide 
better advice?

Either way, at 7000 finding aids, the solution would basically need to be 
automated – if your box ranges are very regular (i.e. only single number or 
range, no “3,4,7-10” or similar), it wouldn’t be too difficult – split the 
range on ‘-‘, generate list of numbers, replace container with multiple 
containers.
--
Dave Mayo (he/him)
Senior Digital Library Software Engineer
Harvard University > HUIT > LTS

From:  on behalf of 
"Lucas, Dawne Howard" 
Reply-To: Archivesspace Users Group 

Date: Thursday, June 18, 2020 at 8:13 AM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Top container ranges


Hi all,



We are formulating a plan to import our 7000+ EAD finding aids into 
ArchivesSpace and are wondering how other institutions have handled top 
container ranges.



For example, we have finding aids coded like this:



3-4Photographs



This imports into ASpace just fine (yay!), but of course also creates a top 
container for Box 3-4 instead of Box 3 and Box 4 (boo!). We assume this will be 
an issue later when we integrate with Aeon.



The most obvious solution to this problem appears to be to change the encoding 
to:



3Photographs



4 
Photographs



For several reasons, this is not a viable solution for us. Have other 
institutions figured out a way to deal with this issue that does not include 
editing the EAD in individual finding aids?

Thanks for your help,

Dawne

--
Dawne Howard Lucas (she/her/hers)
Technical Services Archivist

Wilson Special Collections Library
200 South Road, CB #3926
Chapel Hill, NC 27515
The University of North Carolina at Chapel Hill
P  919-966-1776   E  dawne_lu...@unc.edu

[cid:image001.png@01D5F200.0D957C80]



___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Top container ranges

[Lucas, Dawne Howard]

Thanks, Dave.  I guess I should have specified that changing the EAD isn’t a 
viable solution for us unless it’s automated. We do not plan to edit individual 
finding aids manually except in cases where the ranges aren’t regular.

If you’ve done this at Harvard, have there been any drawbacks? Anything we 
should be looking to avoid?

Thanks again,

Dawne


From: Mayo, Dave
Sent: Thursday, June 18, 2020 9:04 AM
To: Archivesspace Users 
Group
Subject: Re: [Archivesspace_Users_Group] Top container ranges

The two options I see here are essentially:

1. Change the EAD
2. Change the containers after they’re ingested.

Of the two, changing the EAD seems _easier_ to me; if you wouldn’t mind going 
more into why that’s not a viable solution for you, it might help us provide 
better advice?

Either way, at 7000 finding aids, the solution would basically need to be 
automated – if your box ranges are very regular (i.e. only single number or 
range, no “3,4,7-10” or similar), it wouldn’t be too difficult – split the 
range on ‘-‘, generate list of numbers, replace container with multiple 
containers.
--
Dave Mayo (he/him)
Senior Digital Library Software Engineer
Harvard University > HUIT > LTS

From:  on behalf of 
"Lucas, Dawne Howard" 
Reply-To: Archivesspace Users Group 

Date: Thursday, June 18, 2020 at 8:13 AM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Top container ranges


Hi all,



We are formulating a plan to import our 7000+ EAD finding aids into 
ArchivesSpace and are wondering how other institutions have handled top 
container ranges.



For example, we have finding aids coded like this:



3-4Photographs



This imports into ASpace just fine (yay!), but of course also creates a top 
container for Box 3-4 instead of Box 3 and Box 4 (boo!). We assume this will be 
an issue later when we integrate with Aeon.



The most obvious solution to this problem appears to be to change the encoding 
to:



3Photographs



4 
Photographs



For several reasons, this is not a viable solution for us. Have other 
institutions figured out a way to deal with this issue that does not include 
editing the EAD in individual finding aids?

Thanks for your help,

Dawne

--
Dawne Howard Lucas (she/her/hers)
Technical Services Archivist

Wilson Special Collections Library
200 South Road, CB #3926
Chapel Hill, NC 27515
The University of North Carolina at Chapel Hill
P  919-966-1776   E  dawne_lu...@unc.edu

[cid:image001.png@01D5F200.0D957C80]



___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Top container ranges

[Mayo, Dave]

The two options I see here are essentially:

1. Change the EAD
2. Change the containers after they’re ingested.

Of the two, changing the EAD seems _easier_ to me; if you wouldn’t mind going 
more into why that’s not a viable solution for you, it might help us provide 
better advice?

Either way, at 7000 finding aids, the solution would basically need to be 
automated – if your box ranges are very regular (i.e. only single number or 
range, no “3,4,7-10” or similar), it wouldn’t be too difficult – split the 
range on ‘-‘, generate list of numbers, replace container with multiple 
containers.

--
Dave Mayo (he/him)
Senior Digital Library Software Engineer
Harvard University > HUIT > LTS

From:  on behalf of 
"Lucas, Dawne Howard" 
Reply-To: Archivesspace Users Group 

Date: Thursday, June 18, 2020 at 8:13 AM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Top container ranges


Hi all,



We are formulating a plan to import our 7000+ EAD finding aids into 
ArchivesSpace and are wondering how other institutions have handled top 
container ranges.



For example, we have finding aids coded like this:



3-4Photographs



This imports into ASpace just fine (yay!), but of course also creates a top 
container for Box 3-4 instead of Box 3 and Box 4 (boo!). We assume this will be 
an issue later when we integrate with Aeon.



The most obvious solution to this problem appears to be to change the encoding 
to:



3Photographs



4 
Photographs



For several reasons, this is not a viable solution for us. Have other 
institutions figured out a way to deal with this issue that does not include 
editing the EAD in individual finding aids?

Thanks for your help,

Dawne

--
Dawne Howard Lucas (she/her/hers)
Technical Services Archivist

Wilson Special Collections Library
200 South Road, CB #3926
Chapel Hill, NC 27515
The University of North Carolina at Chapel Hill
P  919-966-1776   E  dawne_lu...@unc.edu

[cid:image001.png@01D5F200.0D957C80]


___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Top container ranges

[Lucas, Dawne Howard]

One quick-follow up: we’re not completely clueless about how we might do this, 
but appreciate hearing about the experience at other institutions. For those 
institutions that have done this, were there any drawbacks?

Thanks,

Dawne


From: Lucas, Dawne Howard
Sent: Thursday, June 18, 2020 8:13 AM
To: Archivesspace Users 
Group
Subject: [Archivesspace_Users_Group] Top container ranges


Hi all,



We are formulating a plan to import our 7000+ EAD finding aids into 
ArchivesSpace and are wondering how other institutions have handled top 
container ranges.



For example, we have finding aids coded like this:



3-4Photographs



This imports into ASpace just fine (yay!), but of course also creates a top 
container for Box 3-4 instead of Box 3 and Box 4 (boo!). We assume this will be 
an issue later when we integrate with Aeon.



The most obvious solution to this problem appears to be to change the encoding 
to:



3Photographs



4 
Photographs



For several reasons, this is not a viable solution for us. Have other 
institutions figured out a way to deal with this issue that does not include 
editing the EAD in individual finding aids?

Thanks for your help,

Dawne

--
Dawne Howard Lucas (she/her/hers)
Technical Services Archivist

Wilson Special Collections Library
200 South Road, CB #3926
Chapel Hill, NC 27515
The University of North Carolina at Chapel Hill
P  919-966-1776   E  dawne_lu...@unc.edu

[cid:image001.png@01D5F200.0D957C80]



___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] Top container ranges

[Lucas, Dawne Howard]

Hi all,



We are formulating a plan to import our 7000+ EAD finding aids into 
ArchivesSpace and are wondering how other institutions have handled top 
container ranges.



For example, we have finding aids coded like this:



3-4Photographs



This imports into ASpace just fine (yay!), but of course also creates a top 
container for Box 3-4 instead of Box 3 and Box 4 (boo!). We assume this will be 
an issue later when we integrate with Aeon.



The most obvious solution to this problem appears to be to change the encoding 
to:



3Photographs



4 
Photographs



For several reasons, this is not a viable solution for us. Have other 
institutions figured out a way to deal with this issue that does not include 
editing the EAD in individual finding aids?

Thanks for your help,

Dawne

--
Dawne Howard Lucas (she/her/hers)
Technical Services Archivist

Wilson Special Collections Library
200 South Road, CB #3926
Chapel Hill, NC 27515
The University of North Carolina at Chapel Hill
P  919-966-1776   E  dawne_lu...@unc.edu

[cid:image001.png@01D5F200.0D957C80]


___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group