[Archivesspace_Users_Group] Top Container List question- update

Jessica Wagner Webster jessica.wagnerwebster at baruch.cuny.edu
Wed Sep 11 16:48:09 EDT 2019


Hi all,

In looking at this further, it doesn't actually appear that the barcoder plugin issued multiple top container numbers for the same box, so disregard that part of the question- though each folder was also assigned a top container number by the barcoder. Is that expected? And are there any ways to work on these in batch?

Thanks again,
Jessica

Jessica Wagner Webster
Digital Initiatives Librarian, Assistant Professor
Baruch College, Newman Library
151 East 25th Street, Room 523
New York, NY 10010
(646) 312-1672
Jessica.WagnerWebster at baruch.cuny.edu<mailto:Jessica.WagnerWebster at baruch.cuny.edu>

From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Jessica Wagner Webster
Sent: Wednesday, September 11, 2019 4:41 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Top Container List question

Hi all,

I've been using ASpace for a long time, but only recently were we able to successfully upgrade to the 1.5x iteration and start working with top containers. When we upgraded, we used the barcoder utility as required, which generated top container numbers for our boxes; we don't have actual barcodes on our boxes. I understand that many of you might be past this phase of implementation, and maybe I'm missing some key information!

But I'm wondering now how to generate top container numbers for new cataloging- is there a way to generate these? How do I come up with top container numbers- what are they supposed to refer to, if they're supposed to be unique?

It seems like each box (or equivalent) is supposed to have its own container number and all folders (or equivalent) affiliated with that box are attached to that particular top container. However in our case, it appears that each item-level record was given its own top container number by the barcorder, regardless of the fact that they might have been in the same box? I'm not sure why this would be except as a fluke of our cataloging. If this is true, is there a way to batch edit our top containers to fix this issue?

If anyone could point me toward additional resources on implementing top containers, that would be great, too.

Thanks,
Jessica

Jessica Wagner Webster
Digital Initiatives Librarian, Assistant Professor
Baruch College, Newman Library
151 East 25th Street, Room 523
New York, NY 10010
(646) 312-1672
Jessica.WagnerWebster at baruch.cuny.edu<mailto:Jessica.WagnerWebster at baruch.cuny.edu>

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


More information about the Archivesspace_Users_Group mailing list
http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2019-September/006970.html
lyralists.lyrasis.org
CC-MAIN-2024-10
6738
application/http; msgtype=response
sha1:L2M5HM2ZQXB5V3WE3PQPZYTF5L5OFFUW
<urn:uuid:ddfcd910-8248-41eb-af08-4fded59d35ad>
2024-03-04T14:24:06Z
75.77.204.231
text/html
sha1:N75KGGP6WIHXBKT72CADLFYWSR2QFO6K
<urn:uuid:a10d3da1-7905-4368-abfb-9d6a1457c673>
http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2019-September/006970.html
response
<urn:uuid:a1dce89d-e23e-4ebe-a0b9-743b916f3f8f>
isPartOf: CC-MAIN-2024-10
publisher: Common Crawl
description: Wide crawl of the web for February/March 2024
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-154
software: Apache Nutch 1.19 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.5-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/