Feature #8642

Add relation rows to associate actors with repositories

Added by Mike Gale about 5 years ago. Updated about 3 years ago.

Status:VerifiedStart date:07/03/2015
Priority:MediumDue date:
Assignee:-% Done:

0%

Category:Actor
Target version:Release 2.4.0
Google Code Legacy ID: Tested version:
Sponsored:Yes Requires documentation:

Description

This work will add a 1:M relationship between a repository and an authority record (e.g. actor), to indicate the agency responsible for the creation and/or maintenance of the authority record, and improve certain queries and operations (such as actor matching on imports).

On the back end, we'll accomplish this by adding rows in the relation table. In the user interface, this will incorporate a couple of visible changes:

  • On the actor view and edit pages, the Relationships area will have a new field, where users can add a relationship to a repository via an autocomplete field. Only 1 relationship will be possible - this is meant to indicate the maintaining or creating agency/repository, not all repositories using the authority record via links in their descriptions
  • On the repository view page, we'll include a paginated list of related actors, similar to how the list of actor relationships have been updated in #10048
  • If there is time, we'll also add a facet to the Authority record browse page

subordinate.png (26.9 KB) Dan Gillean, 10/07/2016 04:36 PM


Related issues

Related to Access to Memory (AtoM) - Task #8641: Remove fetching existing actors by repository Verified 07/03/2015
Related to AtoM Wishlist - Feature #4268: Archival description to pull the Institution ID from ISDIAH New
Related to Access to Memory (AtoM) - Feature #10144: Enhance import matching behaviors: Add ability to limit ... Verified 06/10/2016
Related to Access to Memory (AtoM) - Task #10506: Improve actor matching on descriptions import Verified 11/02/2016
Duplicated by AtoM Wishlist - Feature #8702: Create many to many relationships between actors and repo... Duplicate 07/15/2015

History

#1 Updated by Mike Gale about 5 years ago

  • Related to Task #8641: Remove fetching existing actors by repository added

#2 Updated by Mike Gale about 5 years ago

Places we need to revisit after restoring this functionality:

QubitFlatfileImport - createOrFetchActor
XML import
CSV import
METS import(?)
QubitInformationObject - setActorByName

#3 Updated by David Juhasz about 5 years ago

  • Related to Feature #4268: Archival description to pull the Institution ID from ISDIAH added

#4 Updated by David Juhasz about 5 years ago

I think this a duplicate of issue #4268, though the requirements have changed slightly since the original ticket.

#5 Updated by Redmine Admin about 4 years ago

  • Target version deleted (Release 2.3.0)

#6 Updated by Dan Gillean about 4 years ago

  • Category set to Actor
  • Target version set to Release 2.4.0

#7 Updated by Dan Gillean about 4 years ago

  • Sponsored changed from No to Yes

#9 Updated by Dan Gillean almost 4 years ago

  • Related to Feature #10144: Enhance import matching behaviors: Add ability to limit matching to a specific repository or top-level description added

#13 Updated by Dan Gillean almost 4 years ago

  • Target version changed from Release 2.4.0 to Release 2.5.0

#14 Updated by Dan Gillean almost 4 years ago

  • Tracker changed from Task to Feature
  • Description updated (diff)
  • Assignee set to José Raddaoui Marín
  • Requires documentation set to Yes

Updated description to better clarify the feature

#15 Updated by José Raddaoui Marín almost 4 years ago

  • Status changed from New to Code Review
  • Assignee changed from José Raddaoui Marín to Nick Wilkinson

#16 Updated by Nick Wilkinson almost 4 years ago

  • Assignee changed from Nick Wilkinson to Jesús García Crespo

Hi Jesús, assigning to you for CR.

#17 Updated by Jesús García Crespo almost 4 years ago

  • Status changed from Code Review to In progress
  • Assignee changed from Jesús García Crespo to José Raddaoui Marín

LGTM!

#18 Updated by José Raddaoui Marín almost 4 years ago

  • Status changed from In progress to QA/Review
  • Assignee changed from José Raddaoui Marín to Dan Gillean
  • Target version changed from Release 2.5.0 to Release 2.4.0

Merged in qa/2.4.x

#19 Updated by Dan Gillean almost 4 years ago

  • File subordinate.png added
  • Status changed from QA/Review to Feedback
  • Assignee changed from Dan Gillean to José Raddaoui Marín

When adding a repository as the maintainer, upon save it would also display in the relationships area as a hierarchical relationship with a type: [repository] is the subordinate of [actor]." See attached screenshot.

When I tried to edit the record and remove the relationship I got the following error:

[error] 2824#0: *1 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Call to a member function delete() on a non-object in /usr/share/nginx/atom/plugins/sfIsaarPlugin/modules/sfIsaarPlugin/actions/relatedAuthorityRecordComponent.class.php on line 129" while reading response header from upstream, client: 10.10.10.1, server: _, request: "POST /potter-alexander-oberlander/edit HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.atom.sock:", host: "10.10.10.10", referrer: "http://10.10.10.10/potter-alexander-oberlander/edit" 

Expected outcome

No relationship should be visible in the UI Relationships area.

#20 Updated by Dan Gillean almost 4 years ago

  • Status changed from Feedback to Verified
  • Assignee deleted (José Raddaoui Marín)

Update - purged my environment and made sure the database was upgraded, and everything looks fine now! Marking as verified.

#21 Updated by José Raddaoui Marín over 3 years ago

  • Related to Task #10506: Improve actor matching on descriptions import added

#22 Updated by Dan Gillean about 3 years ago

I have documentation for this in a commit I'll be pushing soon. FYI. Will remove the requires documentation tag when I can add a link to the pushed commit.

#23 Updated by Dan Gillean about 3 years ago

  • Duplicated by Feature #8702: Create many to many relationships between actors and repositories added

#24 Updated by Dan Gillean about 3 years ago

  • Requires documentation deleted (Yes)

Also available in: Atom PDF