[Archivesspace_Users_Group] Community review of Rights Management Enhancements specification

[Max Eckard]

Hi Jordan,

Thanks for the feedback! This issue about the pairing of Conditions
Governing Access/Use notes and the Rights module has definitely come up in
our conversations.

Borrowing some language from these conversations, at least for the moment
we see the statements in the ArchivesSpace Rights module being used in
conjunction with rights/access statements supported in the Conditions
Governing Access and Conditions Governing Use notes. The Rights module
statements are for granular, actionable statements, whereas the Conditions
Governing Access/Use notes are for summary, non-actionable statements, and
instructions, where appropriate, for contacting rights holders. That may
turn out to be an unnecessary redundancy, and clearly there are folks like
you that make a good case for that in theory and in practice, but that's at
least our thinking for now.

Thanks again for your input! It really is very much appreciated!
Max

On Tue, Oct 4, 2016 at 11:59 AM, Jordon Steele <jsteele at jhu.edu> wrote:

> Max,
>
>
>
> These enhancements look good to us, thanks for your efforts.
>
>
>
> We’ve been discussing at JHU the overlap and, frankly, similarity between
> what sort of information the Rights Management module is trying to capture
> and the Conditions Governing Access/Use notes are used for, and we’re not
> seeing a difference in concept between the two.  “Archivists have always
> used the Access/Use notes” or “Access/Use notes are an EAD/DACS/AT
> hold-over” may be factually accurate but they are not strong cases for
> continuing use.
>
>
>
> So for the sake of not over-complicating the ASpace data model--where
> equally valid locations for putting the same type of information
> proliferate and, therefore, confuse—my main feedback is that you/the
> community/whoever take a good look at integration between the access/use
> notes and the rights management module. (After review of the responses I
> received from the ASpace listserv and internal discussion, JHU has decide
> to stop using the Access/Use notes and begin to use the Rights sub-records
> to manage information about what people are allowed and not allowed to do
> with all of our collections—analog and digital.) Your work presents a good
> opportunity for us all to try to get on the same page.
>
>
>
> Best,
>
>
>
> Jordon
>
>
>
> Jordon Steele
>
> Hodson Curator of the University Archives
>
> The Sheridan Libraries
>
> Johns Hopkins University
>
> 3400 N Charles St
>
> Baltimore, MD 21218
>
> 410-516-5493
>
> jsteele at jhu.edu
>
>
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:
> archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Max
> Eckard
> *Sent:* Monday, October 03, 2016 2:49 PM
> *To:* Archivesspace Users Group <archivesspace_users_group@
> lyralists.lyrasis.org>
> *Subject:* [Archivesspace_Users_Group] Community review of Rights
> Management Enhancements specification
>
>
>
> Good morning ArchivesSpace community,
>
> You may already be aware that representatives from the ArchivesSpace
> membership, the ArchivesSpace program team and Artefactual, Inc. have been
> working on a specification for enhancing the rights module in
> ArchivesSpace.
>
> The primary aim of this specification is to enable the expression of
> standards-based rights statements that are atomic and actionable and that
> support data transfers with other applications using rights statements,
> such as Archivematica.
>
> We have completed a draft specification, and are now asking for community
> review and feedback.
>
> The attached packet includes:
>
>    - a summary of the enhancements requested in the specification and
>    their purpose;
>    - a spreadsheet containing:
>
>
>    - 1) the data model being proposed for the rights management module in
>       ArchivesSpace,
>       - 2) the data migrations necessary for moving data in the current
>       data model to the new data model,
>       - 3) a chart indicating the data elements to be migrated from
>       Archivematica to ArchivesSpace, and
>       - 4) a data map illustrating how PREMIS rights elements are
>       supported in Archivematica and ArchivesSpace; and
>
>
>    - ten wire frames illustrating how the proposed data model should be
>    reflected in the ArchivesSpace staff interface.
>
> If you need some orientation to the way that PREMIS Rights Statements are
> used (regardless of whether these are authored in ArchivesSpace), see the
> attached PDF.
>
> Please take a look. Brad Westbrook (brad.westbrook at lyrasis.org), Hillel
> Arnold (harnold at rockarch.org) and/or myself (eckardm at umich.edu) are happy
> to answer any questions that you may have and to receive feedback on the
> specification by *Friday, October 21, 2016*.
>
> Regards,
>
> Max Eckard
>
>
> --
>
> *Max Eckard*
> *Assistant Archivist for Digital Curation*
>
>
>
> Bentley Historical Library
>
> 1150 Beal Ave.
> Ann Arbor, MI 48109-2113
> (734) 763-7518
>
> http://bentley.umich.edu/
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>


-- 
*Max Eckard*
*Assistant Archivist for Digital Curation*


Bentley Historical Library
1150 Beal Ave.
Ann Arbor, MI 48109-2113
(734) 763-7518
http://bentley.umich.edu/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20161005/98d59b87/attachment.html>