[Archivesspace_Users_Group] data problem with the migrator

Chris Fitzpatrick Chris.Fitzpatrick at lyrasis.org
Fri Jun 5 08:40:20 EDT 2015


Hi,


Yes, so since RightsStatements aren't "first class" type objects ( they can only exists as associations to resources, archival objects, accessions, etc ), there's not an endpoint directly for them. To remove them, you have to go through the accession/resource/archival object/etc and update that record.


Are you wanting to delete all "Copyrighted" rights statements? Or is there some kind of filter/qualifier we can use to limit which records should be deleted?


b,chris




Chris Fitzpatrick | Developer, ArchivesSpace
Skype: chrisfitzpat  | Phone: 918.236.6048
http://archivesspace.org/
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Callahan, Maureen <maureen.callahan at yale.edu>
Sent: Thursday, June 4, 2015 5:18 PM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] data problem with the migrator

Something for ALL users going into ASpace from AT to be aware of - the AT migrator creates a rights record in ArchivesSpace if the "Rights Transferred" box is checked in AT. (As I mentioned last month, it only brings over the rights transferred note if this box is checked, which is a different kind of problem).

Here's what it looks like (attached, for those without in-line image viewing):

[cid:73B6380F-4D1E-4339-98A5-C0680A19BC3B at its.yale.internal]

Guys, I'm sorry, but there are a ton of terrible assumptions here based on the presence of a clicked checkbox. Just because rights were transferred doesn't mean that COPYRIGHT was transferred (copyright could be transferred to the public domain, for instance), it doesn't mean that the copyright is still active, and I also wouldn't assume that the jurisdiction is the United States.

I'd like to request that the AT migrator be changed to something a little more modest.

We've been working very hard at Yale to get our rights documentation in order and we'd like to keep this in ASpace. This means that I need to delete these often-erroneous rights records.I don't see anything in the API documentation about deleting rights records - could you give me some guidance about the safest way to do so?

Thanks much,
Maureen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150605/6d5a8ea4/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2015-06-04 at 11.10.32 AM.png
Type: image/png
Size: 123447 bytes
Desc: Screen Shot 2015-06-04 at 11.10.32 AM.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150605/6d5a8ea4/attachment.png>


More information about the Archivesspace_Users_Group mailing list