Appraisal tab Backlog pane / ArchivesSpace pane question

[Noah Lasley]

Hi all,

I have a few questions regarding an Archivematica-ArchivesSpace connection. I'm working with local installs of the following:

Archivematica 1.6.1

Archivematica Storage Service 0.10.1

ArchivesSpace 2.1.1

I have successfully connected Archivematica and ArchivesSpace, as I have the ability to search for and edit ArcchivesSpace resources from the ArchivesSpace pane of the Archivematica Appraisal tab.

However, I am having difficulty adding files from the Backlog pane to ArchivesSpace resources and then starting SIPs. 

For one thing, when I create a Digital Object in an ArchivesSpace resource via the ArchivesSpace pane, I do not have the ability to edit the metadata for the newly created object (clicking on "Edit Metadata" does nothing). If I understand the documentation, I should have the ability to edit the title, general note, etc. for Digital Objects created this way, correct?

Secondly, when I drag directories or files from the Backlog pane to a Resource, although the content appears in the ArchivesSpace pane, I am not seeing the subsequent strikethrough in the Backlog pane for corresponding items.

Finally, in my testing, after having moved content from a a Backlog to an ArchivesSpace resource when I click on "Finalize Arrangement" to start SIP for ingest I get the message "Unable to start SIP; check dashboard logs." On looking at the logs (attached), I don't see anything that immediately stands out as an error message or failure.

I'm wondering if any of you have encountered this or similar issues, or have any ideas for what to try next?

I know that my Archivematica and ArchivesSpace instances are at least partly connected because I can search for and manipulate resource records from the Appraisal pane, it's when I go to edit Digital Objects, move content from the Backlog, and start a SIP that I'm running into trouble.

Any thoughts or suggestions?

Thanks!

Noah Lasley

University of Tennessee at Chattanooga

[Max Eckard]

Hi Noah,

For the first problem, it could be two things:

• If you're trying to edit the Digital Object metadata (sounds like you are), you can't. The ArchiveSpace integration here is such that you can edit the ArchivesSpace Archival Object's metadata (i.e., what's listed in the tree of the ArchivesSpace pane), not the Digital Object. 
• If you're trying to edit the Archival Object metadata, you may need to check the Archivematica user's permissions in ArchivesSpace. Our Archivematica user, for example, can edit ArchivesSpace metadata, but can't delete it (which means the "Delete selected" button in the ArchivesSpace pane doesn't work). Maybe yours doesn't have the proper permissions?
  

For the second thing, sometimes it just takes awhile, or you could refresh the backlog pane (e.g., by resubmitting your search). You could also refresh the page, but this means you'll lose your spot in the Backlog and ArchivesSpace panes.

For the final thing, you may want to check your dashboard debug logs, but also the storage service logs (and debug logs) since Archivematica is moving files around at that point. I often find more useful information there.

Hope that helps,

Max

--
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 archivematica+unsubscribe@googlegroups.com.
To post to this group, send email to archiv...@googlegroups.com.
Visit this group at https://groups.google.com/group/archivematica.
For more options, visit https://groups.google.com/d/optout.

--

Max Eckard
Archivist for Digital Curation

1150 Beal Ave.
Ann Arbor, MI 48109-2113
(734) 763-7518

http://bentley.umich.edu/

[Noah Lasley]

Hi Max,

Thank you for your reply--this information is most helpful!

Unfortunately, I am still getting the "Unable to start SIP; check dashboard logs" message when I try to Finalize Arrangement and start a SIP from the ArchivesSpace pane. I followed your advice and looked at the dashboard debug, storage service, and storage service debug logs, and didn't see anything that stood out as an error message. My IT colleague has also restarted all of the services, but the issue persists.

Here is the procedure that I am following: 

1. In Archivematica, create a standard transfer of test content and send to backlog. In ArchivesSpace create a test resource record with one child archival object.

2. In ArchivesSpace pane of the Appraisal tab, click "Add New Digital Object" to item level archival object in test resource record.

3. Drag file (in this case, a single .tif file) from transfer in Backlog pane to Digital Object component in ArchivesSpace pane.

4. Refresh Backlog pane by clicking "Search transfer backlog." Verify strikethrough on file.

5. In the ArchivesSpace pane, select parent archival object containing Digital Object component, and then click "Finalize Arrangement"

6. "Unable to start SIP; check dashboard logs" message appears.

Is there anything that you see I could be doing wrong on my end, or anything else you recommend I try?

Thanks again!

Noah

University of Tennessee at Chattanooga

To unsubscribe from this group and stop receiving emails from it, send an email to archivematic...@googlegroups.com.

To post to this group, send email to archiv...@googlegroups.com.
Visit this group at https://groups.google.com/group/archivematica.
For more options, visit https://groups.google.com/d/optout.

[graham...@wayne.edu]

Noah,

Unbelievably, we just encountered this error this week.  We're not yet using the Appraisal tab in any workflows or production, but were testing it out to get a better sense of the resulting METS from the resulting SIP.  We stumbled on an AJAX call that Archivematica sends to a URL that ends with /copy_from_arrange that had a HTTP 400 error from Chrome's developer tools.

Looking at the response, it informed us that:

{"message": "Provided SIP UUID (12a90f98-4d3a-4202-9629-d3c8518f12d6) belongs to an already-started SIP!", "error": true}

Still not very familiar with the Appraisal tab and unsure what this meant, we tried to associate a file to a newly created Digital Object and it worked successfully.  Though it doesn't address the underlying error, it might be worth trying again with a freshly created Digital Object to see if that at least isolates it?

-Graham 

[Max Eckard]

Hi Noah,

One other thing you could try is using the developer tools on your browser and checking the response Archivematica is getting back for a particular request, i.e., when you click "Finalize Arrangement." This is under "Network" (or similar--I typically use Firefox), and you have to click on a request to bring up the details (and then "Response" to see the response). Sometimes there's useful information there.

For example (and this may be what's going on with you), one thing the ArchivesSpace resource must have in order for the integration to work is an agent with the role of creator. I'm not sure that you can find out that this is exactly what's wrong unless you check the response with the developer tools (in which case you get a more meaningful error message, like this one).

I actually tried to recreate this error to show you an example of what this looks like. I ended up having an example of a different error, but I think you get the idea:

For that, I brought up the developer tools, clicked "Finalize Arrangement," then inspected the 404 error Archivematica got on the request, then clicked "Response" to see the response.

Hope that helps,

Max

To unsubscribe from this group and stop receiving emails from it, send an email to archivematica+unsubscribe@googlegroups.com.

To post to this group, send email to archiv...@googlegroups.com.
Visit this group at https://groups.google.com/group/archivematica.
For more options, visit https://groups.google.com/d/optout.

[Noah Lasley]

Hi All,

Thank you for your help and suggestions--using the web browser developer tools hadn't occurred to me, but this is a very helpful diagnostic tool that I can see coming in handy for all kinds of issues.  

Max, it turns out that my problem was not having an agent with the role of creator. Once I added that field to the top level resource record, I was able to get SIPs started no problem. As a follow-up clarification for the forum, am I correct in understanding that you can only create one SIP per Digital Object using the ArchivesSpace "Finalize Arrangement" option? For example, if I had one resource record that contained several item-level records with Digital Objects with associated backlog content throughout, I wouldn't be able to "Finalize Arrangement" at the top level and create a SIP for the whole resource record, correct? When I've tested the this scenario, I get the error message "Unable to start SIP, no files arranged into record" So it doesn't seem possible to do this. However, I can go through and start SIPs individually for the immediate parent item level record of the Digital Objects.

Additionally, I can't seem to start SIPs with a Digital Object associated at only the top level of the resource record. Trying to do so gives me a 500 error with no additional detail other than "Sorry! Something wrong happened. Please, contact with your administrator" (screenshot attached). Are there any other required values that the ArchivesSpace resource record needs to have, other than agent with the role of creator, title, extent, date, and identifier? Or is this something that just won't work?

Both of these issues strike me as puzzling based on the documentation that reads "SIPs can be created from any level of description (i.e. a SIP can be started for an entire resource or from an archival object within a resource such as a series)."

Thank you for your help and insight!

All best,

Noah

[Max Eckard]

Hi Noah,

Yes, you can only create one SIP per digital object in the Appraisal tab, and you finalize arrangement on its immediate parent (hence the error message you got).

I haven't tried sending a SIP on a digital object associated with an ArchivesSpace resource record, but I suspect you're right, this is just not the way it was designed to work. I don't think this has anything to do with metadata or lack thereof on the resource (besides creator). Archivematica is probably failing for you here because it can't find the metadata it needs on the non-existent archival object, e.g., title, level, etc., or because it's just expecting an archival object, not a resource.

The documentation should probably just say that you can associate digital objects with ArchivesSpace *archival objects* that are at any level. Community members can actually send pull requests to update the documentation, so I can plan to do that for this issue.

Max

To unsubscribe from this group and stop receiving emails from it, send an email to archivematica+unsubscribe@googlegroups.com.

To post to this group, send email to archiv...@googlegroups.com.
Visit this group at https://groups.google.com/group/archivematica.
For more options, visit https://groups.google.com/d/optout.

[Sarah Romkey]

Thanks a ton Max! And thanks for raising the issue Noah.

Cheers,

Sarah

Sarah Romkey, MAS,MLIS

Archivematica Program Manager
Artefactual Systems
604-527-2056

@archivematica / @accesstomemory

[Susan Malsbury]

Hi all, 

I'm reopening this thread because I'm also having this issue and had already troubleshooted the above issues (e.g. have a creator agent, only finalizing one digital object per parent object, etc.). The error I'm getting is similar error to the one Graham mentioned earlier - a 400 error when it tries to post ot http://172.xx.xx.xx/access/archivesspace/-repositories-2-archival_objects-13687/copy_from_arrange/. Creating a fresh digital object on a different resource didn't fix the problem for us. 

Here's the output of the log error: 

INFO      2018-05-25 16:36:36  archivematica.common:storageService:get_location:149:  Storage locations returned: [{u'uuid': u'bede9141-3d93-4160-98e8-02e1abf296c7', u'pipeline': [u'/api/v2/pipeline/0c1f5819-2ee3-4c80-9afc-8382e1a2d3a1/'], u'used': u'0', u'description': u'am3 SharedDirectory', u'space': u'/api/v2/space/b82f957d-526a-4e7a-91fb-8c92efcb1d39/', u'enabled': True, u'quota': None, u'relative_path': u'var/archivematica/sharedDirectory', u'purpose': u'CP', u'path': u'/var/archivematica/sharedDirectory', u'resource_uri': u'/api/v2/location/bede9141-3d93-4160-98e8-02e1abf296c7/'}]

WARNING   2018-05-25 16:36:38  archivematica.common:storageService:copy_files:210:  Could not connect to storage service: Server Error 500: http://xxx.xx.xx.xx:8000/api/v2/location/bede9141-3d93-4160-98e8-02e1abf296c7/ ({"error_message": "Sorry, this request could not be processed. Please try again later."})

ERROR     2018-05-25 16:38:04  django.request:base:handle_uncaught_exception:256:  Internal Server Error: /access/archivesspace/-repositories-2-archival_objects-13687/copy_from_arrange/

Additionally, when I try and preview a file, I get the following error in the Preview File box: "{"message": "Storage service returned 404; check logs?", "success": false}." I expect the two errors are related.

Any insight would be very much appreciated.

All best,

Susan

____________________________________________

Susan Malsbury | The New York Public Library

Digital Archivist, Archives Unit

Library Services Center

31-11 Thomson Avenue, Rm. 202, Long Island City, NY 11101

T: 917.229.9644 | susanm...@nypl.org

[Sarah Romkey]

Hi Susan,

I know this is a few days old now so maybe you've resolved it but since both errors mention the Storage Service I wonder if there's something going on with your SS generally? Can you still store AIPs from that pipeline, can you try moving something out of backlog (without using ArchivesSpace) and see if you can start a SIP just as a test?

Cheers,

Sarah

Sarah Romkey, MAS,MLIS

Archivematica Program Manager
Artefactual Systems
604-527-2056

@archivematica / @accesstomemory

[Susan Malsbury]

Hi Sarah,

Thanks for replying. I had tried your suggestion during my testing and got the same error - I should have stated that in my original email. I've tried to troubleshoot this error in so many ways that I forgot to document them all here! Right now, I'm trying a fresh transfer and seeing if that helps, but I suspect you are right and it is an issue with our SS.

All best,

SUsan