[Archivesspace_Users_Group] Fields carried over to resource record when spawning

[Chris Fitzpatrick]

Hi Miloche,


Thanks for looking at this...

Will double check if  anything in the spec needs changing, but since the feature is not currently following the spec it's certainly a bug.

I definately think deaccessions should not be included and instances don't seem very helpful either ( actually quite harmful ). I don't know about collection management and user defined? Classifications are being transferred as well, which I'm not sure is useful.


I made a bug ticket for these here:

https://www.pivotaltracker.com/story/show/75349402




best,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 Kottman, Miloche <mkottman at ku.edu>
Sent: Monday, July 14, 2014 9:06 PM
To: 'Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org)'
Subject: [Archivesspace_Users_Group] Fields carried over to resource record when spawning

I've been working with Accession records in the Sandbox (version 1.0.9) to see what fields are transferred to the resource record when "spawning".  The documentation indicates only the following fields are mapped to the resource record AND the documentation points out that Deaccession records linked to accession records are not transferred.
Accession record
(field labels)

Resource record
(field labels)

Identifier

(linked under Related Accessions)

Title

Title

Content Description

Note Type="Scope and content note"

Condition Description

Note Type="General physical description note"

Linked sub-records:

  *   Dates

  *   Extents

  *   Rights

Linked sub-records:

  *   Dates

  *   Extents

  *   Rights

Linked records:

  *   Accession to Resource Names

  *   Subjects

Linked records:

  *   Resource to Accession Names

  *   Subjects


However...
When I spawned a record this morning, the following additional sections from the accession record were pulled into the resource record verbatim:

·         Instances

·         Deaccessions

·         Collection management

·         User Defined
I didn't have a Classifications field in the accession record but it's likely it would have transferred also.

Is this behavior a bug or a feature?

--Miloche Kottman
University of Kansas Libraries
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20140721/d79e7482/attachment.html>