Re: [Archivesspace_Users_Group] Container profile guidance

[Olivia S Solis]

Thank you so much! These are very helpful documents! We are about to do a
shelf read to identify all of our containers/their profiles and also wanted
to create a photo-based document for staff.
-Olivia

On Mon, May 22, 2017 at 10:03 PM, Emma Jolley  wrote:

> Hi Olivia
>
>
>
> I’ve attached the Pictures & Manuscripts Branch container guide for staff
> which I hope might of help to you. We may decide to go to a more systematic
> approach (ie Type 1, Type 2) later on but for the initial implementation we
> chose to go with what names that the staff used to refer to the specific
> containers (eg phase box).
>
>
>
> Hope it helps
>
>
>
> Emma
>
>
>
> Let me know if you can’t open the attachments and I’ll resave as RTF
>
>
>
> *Emma Jolley*| Curator of Digital Archives, Pictures and Manuscripts
> Branch|National Library of Australia Canberra ACT 2600
> e: emma.jol...@nla.gov.au|t: 02 6262 1456| www.nla.gov.au/ms
>
> http://www.nla.gov.au/support-us/make-a-collection-offer-
> pictures-and-manuscripts
>
>
>
> *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org [mailto:
> archivesspace_users_group-boun...@lyralists.lyrasis.org] *On Behalf Of *Olivia
> S Solis
> *Sent:* Tuesday, 23 May 2017 7:09 AM
> *To:* Archivesspace Users Group  lyralists.lyrasis.org>
> *Subject:* [Archivesspace_Users_Group] Container profile guidance
>
>
>
> Hello all,
>
>
>
> We at the Briscoe are making progress in our adoption of ArchivesSpace. We
> are about to deal with all of our containers and develop container
> profiles. This may be a broad question, but I was wondering if, when
> developing your container profiles, any of you adhered to any guiding
> principles. If so , what were they?
>
>
>
> For example, did you develop any kind of criteria for how small a box had
> to be to merit a container profile? What about naming container profiles.
> e.g. [brand] [box type]?  Any broad guidance would be appreciated.
>
>
>
> Thanks!
>
> Olivia
>
>
>
> --
>
> Olivia Solis, MSIS
>
> Metadata Coordinator
>
> Dolph Briscoe Center for American History
>
> The University of Texas at Austin
>
> 2300 Red River St. Stop D1100
>
> Austin TX, 78712-1426
>
> (512) 232-8013 <(512)%20232-8013>
>
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>


-- 
Olivia Solis, MSIS
Metadata Coordinator
Dolph Briscoe Center for American History
The University of Texas at Austin
2300 Red River St. Stop D1100
Austin TX, 78712-1426
(512) 232-8013
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Updating containers via archival_object POST

[Detelich, Alicia]

Hi Don,

Are you using Python to make the updates? Can you post what you have tried so 
far? Here’s an example of how to make an update to a single archival object 
instance via Python 3, which worked for me when I tested it this morning:

api_url = your api url…
repo_num = your repository number…

archival_object_json = requests.get(api_url+ 
‘/repositories/repo_num/archival_objects/1987146’, headers=headers).json()

archival_object_json["instances"] = [{"container": {"barcode_1": 
'39002042614314', "container_locations": [{"jsonmodel_type": 
"container_location", "ref": '/locations/9', "start_date": "2015-06-02", 
"status": "current"}], "indicator_1": '2', "type_1": "box"}, "instance_type": 
"mixed_materials", "jsonmodel_type": "instance", "sub_container": 
{"jsonmodel_type": "sub_container", "top_container": {"ref": 
'/repositories/repo_num/top_containers/190797'}}}]

archival_object_data = json.dumps(archival_object_json)

archival_object_update = 
requests.post(api_url+‘/repositories/repo_num/archival_objects/1987146’, 
headers=headers, data=archival_object_data).json()


If you are trying to do something like archival_object_json[‘container’] I 
don’t think it will work, unless maybe you do 
archival_object_json[‘instances’][‘container’] – but I didn’t check on that.

Also, be sure that all data elements you are updating are correct and 
consistent – I tried to make a test update using fake container info and it did 
not work, but when I tried updating the instance with data from an existing top 
container everything went through just fine. I just changed the barcode, top 
container ref, indicator, and location to reflect the data from the other 
container, and it updated. Hope this helps.

P.S. I have a script which makes these kinds of updates in batch by pulling the 
info you wish to update from a CSV. I can clean it up a bit and share if anyone 
is interested…

Alicia Detelich
Archivist
Manuscripts and Archives
Yale University Libraries

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Donald Mennerich
Sent: Monday, May 22, 2017 4:11 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Updating containers via archival_object 
POST

Hello List,
I'm working a data remediation problem via the aspace API I can't seem to get 
any of the values in a container key within an archival_object to update when I 
post. For example, within a json object of type archival_object like:

"container": {
"type_1": "box",
"indicator_1": "1",
"barcode_1": "31142054615128",
"type_2": "folder",
"indicator_2": "14",
"container_locations": [],
"lock_version": 25
}
If I change any of the values and POST, none of the updates seem to persist. 
This doesn't generate an errors, and any changes to the record otherwise seems 
to save. I'm wondering if this is just not possible, and if so, is there 
another endpoint that might be used to update container information?

Thanks, Don

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

Re: [Archivesspace_Users_Group] Updating containers via archival_object POST

[Lora Davis]

Hi Don,

What version of ASpace are you running?  I’m guessing either 1.4.2 with 
container management plugin or 1.5+…

If that is the case, then the problem is that the data you are trying to change 
in the snippet below isn’t actually controlled from within “container” anymore. 
 You’ve actually got to look for & change the “sub_container” and/or the 
“top_containers” record linked to from “sub_container”:

"instances": [
{
  "sub_container": {
"indicator_2": "2",
"type_2": "folder",
"jsonmodel_type": "sub_container",
"top_container": {
  "ref": "/repositories/3/top_containers/12063"
}
  }
}
  ]

So, in the blob you provide below, type_1, indicator_1, and barcode_1 could be 
modified by POSTing to the linked top_container record, and type_2 and 
indicator_2 could be changed by POSTing the AO back with modifications to 
sub_container instead of container.

Yes, it’s a pain.  I’m spending the ocassional down moment working on a script 
to automate some of this for us here (GET record, dump into a csv, processing 
archivists make changes in csv, then it POSTs back to the proper 
records/subrecords), but it is no where ready for primetime yet, and won’t be 
for a while.

Though, if anyone has this work already complete, I’m all ears! ☺

Lora

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Donald Mennerich
Sent: Monday, May 22, 2017 4:11 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Updating containers via archival_object 
POST

Hello List,
I'm working a data remediation problem via the aspace API I can't seem to get 
any of the values in a container key within an archival_object to update when I 
post. For example, within a json object of type archival_object like:

"container": {
"type_1": "box",
"indicator_1": "1",
"barcode_1": "31142054615128",
"type_2": "folder",
"indicator_2": "14",
"container_locations": [],
"lock_version": 25
}
If I change any of the values and POST, none of the updates seem to persist. 
This doesn't generate an errors, and any changes to the record otherwise seems 
to save. I'm wondering if this is just not possible, and if so, is there 
another endpoint that might be used to update container information?

Thanks, Don

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