[Archivesspace_Users_Group] rights types and upgrade to 2.1.1

[Jason Loeffler]

Thanks, Christine. Yes, I observed Payten's notes at ANW-114 and that
clarifies the issue. All records were migrated to new values correctly and
remarkably quickly.

Our remaining issue is with the re-configuration of default value
templates. For interested parties, I've added my notes to ANW-114 that
further clarifies the issue. We were able to resolve our immediate issue
with MySQL queries. Not sure if this is a bug or a feature but it would be
nice to make the rights statements contained in default templates PREMIS
compliant in a future release.

Best, Jason




On Wed, Aug 23, 2017 at 9:37 AM, Christine Di Bella <
christine.dibella at lyrasis.org> wrote:

> Dear Jason,
>
>
>
> Making rights type a non-configurable list was part of the rights
> specification that was distributed prior to this enhanced functionality
> being built into 2.1.0. The intent of this particular change was to
> maximize compatibility with PREMIS, but to allow “other” as a value, the
> specifics of which users could then specify within the Other Rights Basis
> field. Other Rights Basis is a configurable list.
>
>
>
> The JIRA with all the parts of the specification is here:
> https://archivesspace.atlassian.net/browse/ANW-123
>
>
>
> This is the JIRA explaining the migration path: https://archivesspace.
> atlassian.net/browse/ANW-114
>
>
>
> Did your custom rights statements get migrated as Other with an Other
> Rights Basis that matches your previous label? We didn’t receive much
> feedback from people during testing about how their rights migrations went
> and whether what they expected to see was there, though it was something we
> asked for in the original release candidate announcement. During the
> migration, previous rights statement info. is also backed up into a table
> called rights_statement_pre_088. Are you seeing that in your installation?
>
>
>
> We do know that if someone adds or deletes a value to/from a
> non-configurable list (which can’t be done through the Manage Controlled
> Value Lists area in the staff interface, but potentially can be done by
> working directly with the database) that it affects other parts of the
> application, which would explain the other behavior you describe.
>
>
>
> Christine
>
>
>
> Christine Di Bella
>
> ArchivesSpace Program Manager
>
> christine.dibella at lyrasis.org
>
> 800.999.8558 x2905 <(800)%20999-8558>
>
> 678-235-2905 <(678)%20235-2905>
>
> cdibella13 (Skype)
>
>
>
> [image: ASpaceOrgHomeMedium]
>
>
>
>
>
>
>
>
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:
> archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Jason
> Loeffler
> *Sent:* Tuesday, August 22, 2017 3:06 PM
> *To:* Archivesspace Users Group <archivesspace_users_group@
> lyralists.lyrasis.org>
> *Subject:* [Archivesspace_Users_Group] rights types and upgrade to 2.1.1
>
>
>
> Following an upgrade from 1.5.1 to 2.1.1, we're seeing an issue with
> rights statements.
>
>
>
> It looks like the upgrade blows away our custom rights statement rights
> types from the controlled value rights type enumeration leaving us with
> only the new default types: copyright, license, statute, other.
>
>
>
> In practice, attempting to edit default values for resources components
> yields the following
> <https://gist.github.com/minorscience/bbbb86d1380dd8ed3680f33bd3877b1f>.
> This also prevents the creation of new resource components. Furthermore,
> existing records have their rights statement rights type are overwriting
> with 'other'.
>
>
>
> Just wanted to inquire whether this is replicable for anyone else or
> whether there is an additional upgrade task or documentation I'm missing.
>
>
>
> Thanks, JL
>
>
>
> Jason Loeffler
>
> Technology Consultant | The American Academy in Rome
>
> Brooklyn, New York
>
> jason at minorscience.com
>
> (347) 405-0826
>
> minorscience (Skype)
>
>
>
> _______________________________________________
> 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/20170823/0347b0a9/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 13904 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170823/0347b0a9/attachment.jpg>