Creating a Digital Child help

[Patrick Burden]

Good afternoon, I am working on an integration and noticing an issue with the Digital Objects.  I know you can go into the create menu and make a digital object but I do not think there is a way I could get it created as a child for a Resource.

I thought you could use the reorder mode and cut and paste the digital object using two screens but when trying to do it now I was unable to make the jump between the two windows. 

Does anyone have an idea on how to easily do this?

[Aurora Charlow]

Hi Patrick, 

Digital Objects can't be listed as children in a Resource. They function in a similar way to Container Instances. The DO needs to be linked to a resource using the "Instances" element. 

Sincerely, 

Aurora Charlow 

Digital Archivist, Ohio University Libraries

[Paul Sutherland]

Hi Patrick,

Following on from Aurora - I'm curious how you are hoping to use Digital Objects. Is this as digital representations, or as born-digital objects, or some other way?

Paul

--
You received this message because you are subscribed to the Google Groups "Archivesspace_Users_Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to Archivesspace_User...@lyrasislists.org.
To view this discussion visit https://groups.google.com/a/lyrasislists.org/d/msgid/Archivesspace_Users_Group/08ccd2c8-7443-49fb-b594-8500c905fba6n%40lyrasislists.org.

--

Paul Sutherland

Archivist of Indigenous Materials
Center for Native American and Indigenous Research (CNAIR)
American Philosophical Society Library & Museum
105 S. 5th Street, 2nd Floor
Philadelphia, PA 19106

Lenapehoking

215-440-3408

amphilsoc.org/library/CNAIR

cn...@amphilsoc.org

I respectfully acknowledge that I work and reside in Lenapehoking, the homeland of the Lenape people in past, present, and future generations. I ​am grateful for the past and ongoing generosity of numerous Indigenous communities and individuals who have offered guidance, expertise, and opportunities for collaboration that make my work possible.

Learn more about ...

- The Indigenous Subject Guide to our Indigenous collections, updated frequently
- Blog posts by CNAIR staff & fellows
- Fellowships for working with our collections and elsewhere
- Scheduling a visit to our Reading Room to view our collections

- Our Museum, reopening in April 2026 with These Truths: The Declarations of Independence

[Patrick Burden]

>  Following on from Aurora - I'm curious how you are hoping to use Digital Objects. Is this as digital representations, or as born-digital objects, or some other way?

I am actually working on fixing an integration between Archivematica and ArchivesSpace and trying to backward engineer a way to get them connected.  For those who do not want the details feel free to skip the next section. 

As of today Archivematica does connect and create digital objects in ArchivesSpace as long as you are running version 2.5 or earlier.  As an institution that is about to be upgraded to version 4.2 this is not going to work.  We were able to create a middle ware that basically converted the API calls that were 2.5 friendly and modernize them to have it work with 3.5.  Then looking ahead in the Archivematica roadmap one of the key pages is going to be removed for security reason.  This has to do with viewing a tree structure of a collection that no longer is part of the scope.

If you were to do this in 1.18, you would process the files and send it to the backlog (their word not mine) while in the backlog you can pull up a module to connect to ArchivesSpace and search for the Resource record, in Archivematica you can also create a child record and a digital object.  Once that is correct you then can search the backlog for the files in questions and then click and drag the files to the digital object to make the association.  Once all mapped you would then finalize the arrangement and the items will be removed from the backlog and continue to be process (adding technical metadata to a METS.xml) and once completed the values will then be placed in the desired location.

This is not perfect, there are some key values that are not being transferred, while I was trying to brush off my XPath knowledge to help 1.19 stalled that.  The page in which the mapping were to take place is no longer going to be present, so the goal now is to figure out how I can duplicate this process and ensure that the mapping is correct.  Creating the Child objects can be done within ArchivesSpace so that is something I am not worried about. The key is how can I tell Archivematica that this row in a metadata.csv that contains the descriptive metadata that, a) yes this needs to be a digital object and b) place the digital object here,

Once we solve this issue we SHOULD be able to bypass the page that is being used and I can focus on enhancing the metadata being added to ArchivesSpace.  Such as the Checksum, File Format, and create multiple entities to represent the AIP and DIP versions of the file and present a location for internal use only.

Now if you are reading this and have suggestions, please let me know.  We are hoping to contribute this solution upstream to Archivematica so that we are not the only ones to benefit from this.  Let me know if you have any questions.