[Archivesspace_Users_Group] UPDATE: subject term sources not saving

[Prom, Christopher John]

This seems to be a bug in the migration tool.

Below is the json output fro archon for a four part term in my testing DB.  You can see this works in reverse, so that the top level term is last child in the json nest.

Basically, the migration tool it should apply the subject source ID for the ultimate parent to all of the children, grandchildren, etc when it makes the descendant subjects.

This is something that talked about rather confusingly in my schema mapping document (on the subjects tab in cell D15), but must have gotten overlooked in coding and testing:

https://docs.google.com/spreadsheet/ccc?key=0AhC1KfDNI7uZdG5BM0hRUWxwQVV2U3Nid3lld0FOT0E#gid=3

Chris Prom



"13": {
        "ID": "13",
        "Subject": "Subject.Persname.Greatgrandchild",
        "SubjectTypeID": "8",
        "SubjectSourceID": "0",
        "Identifier": "",
        "ParentID": "12",
        "Parent": {
            "ID": "12",
            "Subject": "Subject.Persname.Grandchild-Archon",
            "SubjectTypeID": "8",
            "SubjectSourceID": "0",
            "Identifier": "",
            "ParentID": "11",
            "Parent": {
                "ID": "11",
                "Subject": "Subject.Parsname.Child-Archon",
                "SubjectTypeID": "8",
                "SubjectSourceID": "0",
                "Identifier": "1",
                "ParentID": "8",
                "Parent": {
                    "ID": "8",
                    "Subject": "Subject.Persname-Archon",
                    "SubjectTypeID": "8",
                    "SubjectSourceID": "2",
                    "Identifier": "Subject.PersnameID-Archon",
                    "ParentID": "0",
                    "Parent": null,
                    "Description": "Subject.PersnameDescription-Archon"
                },
                "Description": ""
            },
            "Description": ""
        },
        "Description": ""
    }
On Feb 27, 2015, at 2:58 PM, Matthew J Gorzalski <mGorzalski at lib.siu.edu<mailto:mGorzalski at lib.siu.edu>> wrote:

We’ve discovered the issue with subject term sources not being saved.  Screen shots are attached for illustration.  They are indeed being migrated to ArchivesSpace if the term is an un-faceted main entry.  The source dictionaries are not saved in the faceted terms because Archon’s functionality does not allow you to select a source for subfields.  Archon rightfully assumes that subfields would come from the same source dictionary and follow cataloging rules.  In other words, the main entry sets the standard for the entire faceted string.

For those using Archivist’s Toolkit, does your faceted subject functionality require you to select a source dictionary for subfields?

MATT GORZALSKI
University Archivist

MORRIS LIBRARY
MAIL CODE 6632
SOUTHERN ILLINOIS UNIVERSITY
605 AGRICULTURE DR
CARBONDALE, IL 62901

mgorzalski at lib.siu.edu<mailto:mgorzalski at lib.siu.edu>
P: 618/453-2225
F: 618/453-3440
lib.siu.edu<http://lib.siu.edu>

<terms_001.jpg><terms_002.jpg><terms_003.jpg>_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto: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/20150227/6ae5a52e/attachment.html>