[Archivesspace_Users_Group] Use of "rights statements" module?

Tue Jun 30 19:04:52 EDT 2015

Thanks for these points, Ben--this would definitely be a great thing to
discuss at SAA!

Great point about the potential discrepancy between paper/analog and
digital rights.  After some reflection, I'm wondering how much of an issue
this might be?   We currently only use conditions governing access/use to
record rights information for all our materials.  The additional
functionality of the Yale container plug in helps provide some important
additional information (esp. start/end dates and nature of the restriction)
that I anticipate we would want to use for all materials (and I'm thinking
about some future Aeon-ArchivesSpace integration as I type...).

While we're hoping that our grant project will yield the ability to
automate the creation of PREMIS rights statements (in Archivematica and
possibly passing these to ASpace), I don't know that we would have our
processors use the rights module for paper/analog materials.  Also, these
more extensive machine-actionable (PREMIS) rights statements would be most
useful in a repository environment.

Just some random thoughts--as always, your point of view is much
appreciated!  Take care and happy 4th--

Mike

--
*Michael Shallcross, CA*
*Lead Archivist for Curation*

Bentley Historical Library
1150 Beal Ave.
Ann Arbor, MI 48109-2113
734.936.1344
http://bentley.umich.edu/
http://archival-integration.blogspot.com/

On Sun, Jun 28, 2015 at 9:31 PM, Ben Goldman <bmg17 at psu.edu> wrote:

> Mike,
>
> Admittedly, I haven't fully thought this through, but my immediate
> reaction is that your notion of locating rights statements in a repository
> might create a discrepancy between how we manage rights statements for
> digital materials and how we manage them for analog. My inclination would
> be to make the ASpace rights statements more PREMIS-compliant, as Hillel
> suggests, at least in order to make the potential cross-walking from
> Archivematica/PREMIS/repository/etc. a little less 'fancy'.
>
> Incidentally, this is the kind of conversation I hope this community might
> have if/when it begins to consider integration with other software (at SAA
> on Saturday afternoon or beyond). A question I keep coming back to when
> thinking about digital workflows, particularly in relation to our emerging
> repository platform at Penn State, is which system should be considered the
> system of record for different types of metadata? I guess in this example,
> I'm thinking ASpace makes the most sense for rights statements, given the
> way we want our staff and researchers to use data in (and derived from)
> ASpace. But I'd love to hear more thoughts on this.
>
> Finally, I wonder if DPLA's proposed interoperable rights statements might
> be relevant to any examination of the rights statements field in ASpace?
> Maybe? Maybe not?
>
> -Ben
>
> Ben Goldman
> Digital Records Archivist
> Penn State University Libraries
>
> ------------------------------
> *From: *"Hillel Arnold" <harnold at rockarch.org>
> *To: *"Archivesspace Users Group" <
> archivesspace_users_group at lyralists.lyrasis.org>
> *Sent: *Thursday, June 25, 2015 5:12:57 PM
> *Subject: *Re: [Archivesspace_Users_Group] Use of "rights statements"
> module?
>
> Hi Mike,
> Your email is incredibly timely! We’re thinking about very similar things
> and I’d love to talk more in detail about your use cases and see where they
> might align with ours.
> An additional approach we’ve discussed is more closely aligning Rights
> statements in AS with PREMIS, so that they’re PREMIS-compliant rather than
> PREMIS-ish.
> I’d be happy to set up a call with you (and whoever else is interested) to
> talk through this a little more and see how we can coordinate!
>
> Hillel Arnold
> Lead Digital Archivist
> Rockefeller Archive Center
>
> From: Michael Shallcross <shallcro at umich.edu>
> Reply-To: Archivesspace Users Group <
> archivesspace_users_group at lyralists.lyrasis.org>
> Date: Thursday, June 25, 2015 at 4:43 PM
> To: Archivesspace Users Group <
> archivesspace_users_group at lyralists.lyrasis.org>
> Subject: [Archivesspace_Users_Group] Use of "rights statements" module?
>
> Greetings, all; we've been exploring the rights statement module in ASpace
> as part of our ASpace-Archivematica grant project and had some questions.
> A lot of questions, to be more precise...
>
> Is anyone currently using (or planning to use) rights statements
> associated with archival objects and/or digital objects?
>
> If yes to the above, would this be in conjunction with conditions
> governing access/use statements?
>
> We've been exploring the wonderful world of the Yale container plugin; the
> ability to add start/end dates for restrictions and identify types of
> restrictions encompasses some of the basic features of the rights
> statements.
>
> We've also been working with Artefactual Systems to explore how
> Archivematica PREMIS rights information maps to the ASpace rights
> statements.  It appears that the latter are 'PREMIS-like' but not really
> PREMIS compliant...  which has brought us to kick around the idea that
> PREMIS rights might be most appropriate to record in the Archivematica AIP
> METS (and passed along to a repository) instead of trying to do some fancy
> crosswalking into ASpace.
>
> Any thoughts/ideas would be most gratefully appreciated.  Thanks!
>
> Mike
>
>
> --
> *Michael Shallcross, CA*
> *Lead Archivist for Curation*
>
>
> Bentley Historical Library
> 1150 Beal Ave.
> Ann Arbor, MI 48109-2113
> 734.936.1344
> http://bentley.umich.edu/
> http://archival-integration.blogspot.com/
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150630/9f60ada0/attachment.html>