Issue indexing metadata of an arranged SIP

[Karla Roig]

Hello all! I have encountered an issue that I would like some help with. 

For context, at my institution we are still in our Archivematica testing phase, but implementation is imminent. My library’s IT has set up AM in a Kubernetes cluster, if it’s of any relevance to this issue.

I am running the following workflow with the intention of versioning born-digital material packages: Run full re-ingest of an archived AIP. Send re-ingested transfer into Backlog. Submit new transfer package and send to Backlog. In Appraisal, arrange both the re-ingested package and the new transfer package into a single SIP and send to Ingest. SIP becomes AIP and is stored and indexed in Archival Storage. 

Both the re-ingested AIP and the new transfer package have their own individual metadata.csv files. If these packages were to be processed individually, these metadata.csv files get indexed into the AIP METS file with no issue. However, arranging the packages together into a single SIP and eventual AIP, their metadata.csv files do not get indexed into the AIP METS file. I have also attempted creating a new metadata.csv for the merged SIP and providing it during the “Add final metadata” microservice to no avail. I am unsure what exactly is the right file path to provide in this scenario.

I have also tested this in a simpler, maybe more expected use case, of submitting two new transfer packages (with their own metadata.csv files) and sending them to Backlog, arranging them together into a single SIP, sending to Ingest and creating the AIP. The metadata was still not indexed into the AIP METS. 

Has anyone done a similar workflow before? Is this expected behavior from Archivematica or a bug? Any help or insight is appreciated.

Thank you!

-Karla

[Susan Borda]

FYI, Karla mentioned this at the June Archivematica User Group meeting. There were only a few of us there, and we didn't know the answer, so we suggested she email the forum. 

-susan 

--
You received this message because you are subscribed to the Google Groups "archivematica" group.
To unsubscribe from this group and stop receiving emails from it, send an email to archivematic...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/archivematica/d25b88dc-e8a9-4c17-8985-03ad1675064an%40googlegroups.com.

--

Susan Borda

Digital Preservation Projects Manager

Digital Preservation Unit

University of Michigan Libraries

Buhr Building

sbo...@umich.edu

My office phone number is temporarily disconnected while I work remotely due to COVID-19. Please contact me via email.

 

[Sarah Romkey]

Hello Karla,

Thanks for your question. You're attempting something that is not currently support (sending AIP in reingest to backlog and re-arranging/selecting) and I suspect that would be why you're running into this issue- see the "Important" note in the Full Re-ingest section of the documentation: https://archivematica.org/en/docs/archivematica-1.17/user-manual/ingest/ingest/#full-re-ingest

Your simpler use case should work though. My guess is that the trouble is with the file paths in the csv. I'm not sure if the issue would be with the placement in backlog, or something related to a Kubernetes based deployment. Are you able to include a sample/example of your metadata.csv file, I could take a look and see if anything is sticking out to me.

Cheers,

Sarah

Sarah Romkey, MAS,MLIS

Head of Hosting and SaaS Products

She/her
Artefactual Systems
604-527-2056

To view this discussion visit https://groups.google.com/d/msgid/archivematica/CAKicayx3qNMNk_OaW5tGYM91vUH6-WMz3_1un2%3DGrCvZj8o-sA%40mail.gmail.com.

[Karla Roig]

Hi Sarah,

Ah, thank you for providing this information! This definitely clears some things up regarding my AIP re-ingest attempts (though they were successful despite the lack of metadata indexing). 

As for the simpler case, I am attaching an example of one of the individual metadata.csv files from the original transfer packages before they get arranged together in the Appraisal tab. Some additional variables for this simpler test case I did: it was of two unzipped bag packages, I have confirmed I am adding the metadata folder and metadata.csv at the correct level because I have tested it successfully, and the merged AIP METS did successfully index the original bag-info.txt of both of these transfers. 

- Karla