Re: [Archivesspace_Users_Group] merge Top Container functionality
This is great news! - thank you for the update on this, Christine. We wanted to add our voices to the chorus that we too are looking forward to this functionality. We would also very much welcome the ability to merge container profiles, as Kevin just brought up. Thanks, Rachel On Wed, Jun 5, 2019 at 8:21 AM Christine Di Bella < christine.dibe...@lyrasis.org> wrote: > For container management improvements, merging top containers has been the > priority for awhile based on the Staff Interface Enhancement Working Group > recommendations and what we've heard from the community -- that's > definitely what we're aiming for first. But, as you note, there's a JIRA > for merging container profiles as well. We'll need to revisit this when we > get there, but I'd think that once we get top containers worked out, adding > the ability to merge container profiles would be a comparatively short step > from there. > > (Of course, if a community developer is able to tackle merging container > profiles before we get there, we 'd love to hear from them. The program > team or community members could likely create a more detailed specification > for how it should look/behave based on what's in the JIRA.) > > Christine > > -Original Message- > From: archivesspace_users_group-boun...@lyralists.lyrasis.org < > archivesspace_users_group-boun...@lyralists.lyrasis.org> On Behalf Of > Kevin Clair > Sent: Tuesday, June 4, 2019 7:48 PM > To: Archivesspace Users Group < > archivesspace_users_group@lyralists.lyrasis.org> > Subject: Re: [Archivesspace_Users_Group] merge Top Container functionality > > Thanks, Christine! Will there be similar functionality for Container > Profiles? Someone at our shop asked me about that the other day and I saw > there's a ticket for it at > https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_ANW-2D550=DwIGaQ=slrrB7dE8n7gBJbeO0g-IQ=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk=WzsSfhV5voLsah7Ip9vFy81tN7BDqOAUmc829ruDPKo=0e1WDtwfatT5pXluM5NJQ8U6w6Aq7hlx6hjwS_PwgFI= > , but it looks like it hasn't been updated since last summer. -k > > On 6/4/19, 2:50 PM, " > archivesspace_users_group-boun...@lyralists.lyrasis.org on behalf of > Christine Di Bella" < > archivesspace_users_group-boun...@lyralists.lyrasis.org on behalf of > christine.dibe...@lyrasis.org> wrote: > > Hi Benn, > > Merging Top Containers has been on our development roadmap, and we > know it is of great interest to a number of people in the community, but > until recently we had not been able to identify a developer to take this > on. We've now determined that we will be able to work on this after some of > the large projects related to agents and infrastructure that are currently > in progress have been completed. We're aiming for this functionality to be > available in the application later this year. > > Christine > > Christine Di Bella > ArchivesSpace Program Manager > christine.dibe...@lyrasis.org > 800.999.8558 x2905 > 678-235-2905 > cdibella13 (Skype) > > > > -Original Message- > From: archivesspace_users_group-boun...@lyralists.lyrasis.org < > archivesspace_users_group-boun...@lyralists.lyrasis.org> On Behalf Of > Benn Joseph > Sent: Tuesday, May 21, 2019 5:22 PM > To: Archivesspace Users Group < > archivesspace_users_group@lyralists.lyrasis.org> > Subject: [Archivesspace_Users_Group] merge Top Container functionality > > Hi all, > I'm curious whether there are any updates re: the ability to merge Top > Containers. It looks like ANW-462 deals specifically with this but I can't > tell if there has been much activity on it lately: > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_ANW-2D462-3FatlOrigin-3DeyJpIjoiZTc0MWQ4MDdlMjhjNGFlZmE4YTEwYzg3YTQ0ZmQzZTkiLCJwIjoiaiJ9=DwIGaQ=slrrB7dE8n7gBJbeO0g-IQ=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk=WzsSfhV5voLsah7Ip9vFy81tN7BDqOAUmc829ruDPKo=B-W8Y4bxQ_l6xQ-rv-XOPKDsOq4yF4EJxCKeQnJnKIw= > > Thanks! > --Benn > > Benn Joseph > Head of Archival Processing > Northwestern University Libraries > Northwestern University > > https://urldefense.proofpoint.com/v2/url?u=http-3A__www.library.northwestern.edu=DwIGaQ=slrrB7dE8n7gBJbeO0g-IQ=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk=WzsSfhV5voLsah7Ip9vFy81tN7BDqOAUmc829ruDPKo=6YgNz1fy5Ld4xc-vCQ2ZXPR7HADFt1gIsPzEPtV_dKQ= > benn.jos...@northwestern.edu > 847.467.6581 > > > > -Original Message- > From: archivesspace_users_group-boun...@lyralists.lyrasis.org < > archivesspace_users_group-boun...@lyralists.lyrasis.org> On Behalf Of >
Re: [Archivesspace_Users_Group] merge Top Container functionality
For container management improvements, merging top containers has been the priority for awhile based on the Staff Interface Enhancement Working Group recommendations and what we've heard from the community -- that's definitely what we're aiming for first. But, as you note, there's a JIRA for merging container profiles as well. We'll need to revisit this when we get there, but I'd think that once we get top containers worked out, adding the ability to merge container profiles would be a comparatively short step from there. (Of course, if a community developer is able to tackle merging container profiles before we get there, we 'd love to hear from them. The program team or community members could likely create a more detailed specification for how it should look/behave based on what's in the JIRA.) Christine -Original Message- From: archivesspace_users_group-boun...@lyralists.lyrasis.org On Behalf Of Kevin Clair Sent: Tuesday, June 4, 2019 7:48 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] merge Top Container functionality Thanks, Christine! Will there be similar functionality for Container Profiles? Someone at our shop asked me about that the other day and I saw there's a ticket for it at https://archivesspace.atlassian.net/browse/ANW-550, but it looks like it hasn't been updated since last summer. -k On 6/4/19, 2:50 PM, "archivesspace_users_group-boun...@lyralists.lyrasis.org on behalf of Christine Di Bella" wrote: Hi Benn, Merging Top Containers has been on our development roadmap, and we know it is of great interest to a number of people in the community, but until recently we had not been able to identify a developer to take this on. We've now determined that we will be able to work on this after some of the large projects related to agents and infrastructure that are currently in progress have been completed. We're aiming for this functionality to be available in the application later this year. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibe...@lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) -Original Message- From: archivesspace_users_group-boun...@lyralists.lyrasis.org On Behalf Of Benn Joseph Sent: Tuesday, May 21, 2019 5:22 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] merge Top Container functionality Hi all, I'm curious whether there are any updates re: the ability to merge Top Containers. It looks like ANW-462 deals specifically with this but I can't tell if there has been much activity on it lately: https://archivesspace.atlassian.net/browse/ANW-462?atlOrigin=eyJpIjoiZTc0MWQ4MDdlMjhjNGFlZmE4YTEwYzg3YTQ0ZmQzZTkiLCJwIjoiaiJ9 Thanks! --Benn Benn Joseph Head of Archival Processing Northwestern University Libraries Northwestern University www.library.northwestern.edu benn.jos...@northwestern.edu 847.467.6581 -Original Message- From: archivesspace_users_group-boun...@lyralists.lyrasis.org On Behalf Of Tang, Lydia Sent: Wednesday, January 16, 2019 12:18 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container Management Enhancements - Call for Community Input I second the ability to merge containers! Lydia From: on behalf of Valerie Addonizio Reply-To: Archivesspace Users Group Date: Wednesday, January 16, 2019 at 1:17 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container Management Enhancements - Call for Community Input I know that the comment period is closed, but this seemed like a logical place to ask whether the idea of container merging functionality was considered as part of this effort (I know it is not in the scope of work, but was it considered and not selected?) and whether other institutions are in need of such functionality? From: archivesspace_users_group-boun...@lyralists.lyrasis.org [mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of Bowers, Kate A. Sent: Thursday, December 20, 2018 4:16 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container Management Enhancements - Call for Community Input Dear ArchivesSpace community: Apologies for the length of this. I’ll try to address a lot of comments, but not all! Please let me know if (as they may well do) my elaborations only elicit more questions! In general, most of these proposals are derived from facing problems of scale. Harvard has 30 repositories and over 200 users of ArchivesSpace. Others have to do with managing “medium rare” materials’ locations and containers in ArchivesSpace
Re: [Archivesspace_Users_Group] merge Top Container functionality
Thanks, Christine! Will there be similar functionality for Container Profiles? Someone at our shop asked me about that the other day and I saw there's a ticket for it at https://archivesspace.atlassian.net/browse/ANW-550, but it looks like it hasn't been updated since last summer. -k On 6/4/19, 2:50 PM, "archivesspace_users_group-boun...@lyralists.lyrasis.org on behalf of Christine Di Bella" wrote: Hi Benn, Merging Top Containers has been on our development roadmap, and we know it is of great interest to a number of people in the community, but until recently we had not been able to identify a developer to take this on. We've now determined that we will be able to work on this after some of the large projects related to agents and infrastructure that are currently in progress have been completed. We're aiming for this functionality to be available in the application later this year. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibe...@lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) -Original Message- From: archivesspace_users_group-boun...@lyralists.lyrasis.org On Behalf Of Benn Joseph Sent: Tuesday, May 21, 2019 5:22 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] merge Top Container functionality Hi all, I'm curious whether there are any updates re: the ability to merge Top Containers. It looks like ANW-462 deals specifically with this but I can't tell if there has been much activity on it lately: https://archivesspace.atlassian.net/browse/ANW-462?atlOrigin=eyJpIjoiZTc0MWQ4MDdlMjhjNGFlZmE4YTEwYzg3YTQ0ZmQzZTkiLCJwIjoiaiJ9 Thanks! --Benn Benn Joseph Head of Archival Processing Northwestern University Libraries Northwestern University www.library.northwestern.edu benn.jos...@northwestern.edu 847.467.6581 -Original Message- From: archivesspace_users_group-boun...@lyralists.lyrasis.org On Behalf Of Tang, Lydia Sent: Wednesday, January 16, 2019 12:18 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container Management Enhancements - Call for Community Input I second the ability to merge containers! Lydia From: on behalf of Valerie Addonizio Reply-To: Archivesspace Users Group Date: Wednesday, January 16, 2019 at 1:17 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container Management Enhancements - Call for Community Input I know that the comment period is closed, but this seemed like a logical place to ask whether the idea of container merging functionality was considered as part of this effort (I know it is not in the scope of work, but was it considered and not selected?) and whether other institutions are in need of such functionality? From: archivesspace_users_group-boun...@lyralists.lyrasis.org [mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of Bowers, Kate A. Sent: Thursday, December 20, 2018 4:16 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container Management Enhancements - Call for Community Input Dear ArchivesSpace community: Apologies for the length of this. I’ll try to address a lot of comments, but not all! Please let me know if (as they may well do) my elaborations only elicit more questions! In general, most of these proposals are derived from facing problems of scale. Harvard has 30 repositories and over 200 users of ArchivesSpace. Others have to do with managing “medium rare” materials’ locations and containers in ArchivesSpace. (Medium-rare is a tongue-in-cheek term used to cover materials that might exist in multiple manifestations but that have archival or rare characteristics or treatment. Examples include entire libraries ingested into an archives, author’s own copies of their books, annotated books, or the record copy of serials or reports kept by institutional archives.) • Multi-field top container indicators Some commenters wondered if the multiple fields were to accommodate child containers. To clarify, the suggestion was to facilitate parsing top container identifiers. As a few commenters have surmised, this is to cope with legacy numbers. These are especially common on medium-rare materials. One suggestion was to use a sort algorithm that would obviate the need for separated fields for data. However, because there would be is more than one algorithm necessary over the installation, such a solution would require an added field to identify the algorithm and probably a third field retain a value derived by the algorithm to be sorted alphanumeric
Re: [Archivesspace_Users_Group] merge Top Container functionality
This is great news--thanks Christine! --Benn -Original Message- From: archivesspace_users_group-boun...@lyralists.lyrasis.org On Behalf Of Christine Di Bella Sent: Tuesday, June 04, 2019 3:50 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] merge Top Container functionality Hi Benn, Merging Top Containers has been on our development roadmap, and we know it is of great interest to a number of people in the community, but until recently we had not been able to identify a developer to take this on. We've now determined that we will be able to work on this after some of the large projects related to agents and infrastructure that are currently in progress have been completed. We're aiming for this functionality to be available in the application later this year. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibe...@lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) -Original Message- From: archivesspace_users_group-boun...@lyralists.lyrasis.org On Behalf Of Benn Joseph Sent: Tuesday, May 21, 2019 5:22 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] merge Top Container functionality Hi all, I'm curious whether there are any updates re: the ability to merge Top Containers. It looks like ANW-462 deals specifically with this but I can't tell if there has been much activity on it lately: https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_ANW-2D462-3FatlOrigin-3DeyJpIjoiZTc0MWQ4MDdlMjhjNGFlZmE4YTEwYzg3YTQ0ZmQzZTkiLCJwIjoiaiJ9=DwIGaQ=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws=fciHLC2ou0tXKp-JlPlsrEmslFw9tnR331DgXAhVLvo=JsdQrq3-4cQNlnTtW_etByY6HRDT9SoyTiaqfiwb5y0=I-fDdOiQzR-Odd9-5gE0AXg2ze9rU3Euw_qY32UHQVc= Thanks! --Benn Benn Joseph Head of Archival Processing Northwestern University Libraries Northwestern University http://www.library.northwestern.edu benn.jos...@northwestern.edu 847.467.6581 -Original Message- From: archivesspace_users_group-boun...@lyralists.lyrasis.org On Behalf Of Tang, Lydia Sent: Wednesday, January 16, 2019 12:18 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container Management Enhancements - Call for Community Input I second the ability to merge containers! Lydia From: on behalf of Valerie Addonizio Reply-To: Archivesspace Users Group Date: Wednesday, January 16, 2019 at 1:17 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container Management Enhancements - Call for Community Input I know that the comment period is closed, but this seemed like a logical place to ask whether the idea of container merging functionality was considered as part of this effort (I know it is not in the scope of work, but was it considered and not selected?) and whether other institutions are in need of such functionality? From: archivesspace_users_group-boun...@lyralists.lyrasis.org [mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of Bowers, Kate A. Sent: Thursday, December 20, 2018 4:16 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container Management Enhancements - Call for Community Input Dear ArchivesSpace community: Apologies for the length of this. I’ll try to address a lot of comments, but not all! Please let me know if (as they may well do) my elaborations only elicit more questions! In general, most of these proposals are derived from facing problems of scale. Harvard has 30 repositories and over 200 users of ArchivesSpace. Others have to do with managing “medium rare” materials’ locations and containers in ArchivesSpace. (Medium-rare is a tongue-in-cheek term used to cover materials that might exist in multiple manifestations but that have archival or rare characteristics or treatment. Examples include entire libraries ingested into an archives, author’s own copies of their books, annotated books, or the record copy of serials or reports kept by institutional archives.) • Multi-field top container indicators Some commenters wondered if the multiple fields were to accommodate child containers. To clarify, the suggestion was to facilitate parsing top container identifiers. As a few commenters have surmised, this is to cope with legacy numbers. These are especially common on medium-rare materials. One suggestion was to use a sort algorithm that would obviate the need for separated fields for data. However, because there would be is more than one algorithm necessary over the installation, such a solution would require an added field to identify the algorithm and probably a third field retain a value derived by the algorithm to be sorted alphanumerically. Thus, the direct 3-field solution seems simpler. (A 4-field suggestion was mooted in the committee as potentially more useful communally.) It does
Re: [Archivesspace_Users_Group] merge Top Container functionality
Hi Benn, Merging Top Containers has been on our development roadmap, and we know it is of great interest to a number of people in the community, but until recently we had not been able to identify a developer to take this on. We've now determined that we will be able to work on this after some of the large projects related to agents and infrastructure that are currently in progress have been completed. We're aiming for this functionality to be available in the application later this year. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibe...@lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) -Original Message- From: archivesspace_users_group-boun...@lyralists.lyrasis.org On Behalf Of Benn Joseph Sent: Tuesday, May 21, 2019 5:22 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] merge Top Container functionality Hi all, I'm curious whether there are any updates re: the ability to merge Top Containers. It looks like ANW-462 deals specifically with this but I can't tell if there has been much activity on it lately: https://archivesspace.atlassian.net/browse/ANW-462?atlOrigin=eyJpIjoiZTc0MWQ4MDdlMjhjNGFlZmE4YTEwYzg3YTQ0ZmQzZTkiLCJwIjoiaiJ9 Thanks! --Benn Benn Joseph Head of Archival Processing Northwestern University Libraries Northwestern University www.library.northwestern.edu benn.jos...@northwestern.edu 847.467.6581 -Original Message- From: archivesspace_users_group-boun...@lyralists.lyrasis.org On Behalf Of Tang, Lydia Sent: Wednesday, January 16, 2019 12:18 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container Management Enhancements - Call for Community Input I second the ability to merge containers! Lydia From: on behalf of Valerie Addonizio Reply-To: Archivesspace Users Group Date: Wednesday, January 16, 2019 at 1:17 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container Management Enhancements - Call for Community Input I know that the comment period is closed, but this seemed like a logical place to ask whether the idea of container merging functionality was considered as part of this effort (I know it is not in the scope of work, but was it considered and not selected?) and whether other institutions are in need of such functionality? From: archivesspace_users_group-boun...@lyralists.lyrasis.org [mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of Bowers, Kate A. Sent: Thursday, December 20, 2018 4:16 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container Management Enhancements - Call for Community Input Dear ArchivesSpace community: Apologies for the length of this. I’ll try to address a lot of comments, but not all! Please let me know if (as they may well do) my elaborations only elicit more questions! In general, most of these proposals are derived from facing problems of scale. Harvard has 30 repositories and over 200 users of ArchivesSpace. Others have to do with managing “medium rare” materials’ locations and containers in ArchivesSpace. (Medium-rare is a tongue-in-cheek term used to cover materials that might exist in multiple manifestations but that have archival or rare characteristics or treatment. Examples include entire libraries ingested into an archives, author’s own copies of their books, annotated books, or the record copy of serials or reports kept by institutional archives.) • Multi-field top container indicators Some commenters wondered if the multiple fields were to accommodate child containers. To clarify, the suggestion was to facilitate parsing top container identifiers. As a few commenters have surmised, this is to cope with legacy numbers. These are especially common on medium-rare materials. One suggestion was to use a sort algorithm that would obviate the need for separated fields for data. However, because there would be is more than one algorithm necessary over the installation, such a solution would require an added field to identify the algorithm and probably a third field retain a value derived by the algorithm to be sorted alphanumerically. Thus, the direct 3-field solution seems simpler. (A 4-field suggestion was mooted in the committee as potentially more useful communally.) It does occur to me that there just might not be enough really old, really big repositories with lots of legacy identifiers in the ArchivesSpace community for the parsing of legacy numbers to be a common problem. I appreciate the recognition that a plug-in might be needed instead, but it would be worth hearing from any repositories with similar issues. • Container and location profiles by repository We were envisioning a one-to-one profile-to-repository scenario. Due to the ArchivesSpace staff user interface requirement that one identify only
[Archivesspace_Users_Group] merge Top Container functionality
Hi all, I'm curious whether there are any updates re: the ability to merge Top Containers. It looks like ANW-462 deals specifically with this but I can't tell if there has been much activity on it lately: https://archivesspace.atlassian.net/browse/ANW-462?atlOrigin=eyJpIjoiZTc0MWQ4MDdlMjhjNGFlZmE4YTEwYzg3YTQ0ZmQzZTkiLCJwIjoiaiJ9 Thanks! --Benn Benn Joseph Head of Archival Processing Northwestern University Libraries Northwestern University www.library.northwestern.edu benn.jos...@northwestern.edu 847.467.6581 -Original Message- From: archivesspace_users_group-boun...@lyralists.lyrasis.org On Behalf Of Tang, Lydia Sent: Wednesday, January 16, 2019 12:18 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container Management Enhancements - Call for Community Input I second the ability to merge containers! Lydia From: on behalf of Valerie Addonizio Reply-To: Archivesspace Users Group Date: Wednesday, January 16, 2019 at 1:17 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container Management Enhancements - Call for Community Input I know that the comment period is closed, but this seemed like a logical place to ask whether the idea of container merging functionality was considered as part of this effort (I know it is not in the scope of work, but was it considered and not selected?) and whether other institutions are in need of such functionality? From: archivesspace_users_group-boun...@lyralists.lyrasis.org [mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of Bowers, Kate A. Sent: Thursday, December 20, 2018 4:16 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container Management Enhancements - Call for Community Input Dear ArchivesSpace community: Apologies for the length of this. I’ll try to address a lot of comments, but not all! Please let me know if (as they may well do) my elaborations only elicit more questions! In general, most of these proposals are derived from facing problems of scale. Harvard has 30 repositories and over 200 users of ArchivesSpace. Others have to do with managing “medium rare” materials’ locations and containers in ArchivesSpace. (Medium-rare is a tongue-in-cheek term used to cover materials that might exist in multiple manifestations but that have archival or rare characteristics or treatment. Examples include entire libraries ingested into an archives, author’s own copies of their books, annotated books, or the record copy of serials or reports kept by institutional archives.) • Multi-field top container indicators Some commenters wondered if the multiple fields were to accommodate child containers. To clarify, the suggestion was to facilitate parsing top container identifiers. As a few commenters have surmised, this is to cope with legacy numbers. These are especially common on medium-rare materials. One suggestion was to use a sort algorithm that would obviate the need for separated fields for data. However, because there would be is more than one algorithm necessary over the installation, such a solution would require an added field to identify the algorithm and probably a third field retain a value derived by the algorithm to be sorted alphanumerically. Thus, the direct 3-field solution seems simpler. (A 4-field suggestion was mooted in the committee as potentially more useful communally.) It does occur to me that there just might not be enough really old, really big repositories with lots of legacy identifiers in the ArchivesSpace community for the parsing of legacy numbers to be a common problem. I appreciate the recognition that a plug-in might be needed instead, but it would be worth hearing from any repositories with similar issues. • Container and location profiles by repository We were envisioning a one-to-one profile-to-repository scenario. Due to the ArchivesSpace staff user interface requirement that one identify only a single repository at login, it is extremely easy for users to forget the impact they might have beyond their repository if they change or delete a shared record. We have already experienced mistaken mergers and deletions of agents due to the design of AS staff user interface that does not allow one to see where the record may be linked beyond their repository. For this reason, it is wise to be able to limit changes and deletions of location profiles and container profiles impact to the same chosen repository. • Inactive As Maureen wisely intuited, inactive locations are necessary to recording a complete location history. However, there are additional use cases. When a repository is renovating, for example (as is happening now at the Schlesinger Library) the shelves in a location may be inactive for a time and become active again when the building re-opens. Other
