<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
I think you need to use Texas or France as subdivisions of the subject. The scope note is just a note/comment for documentation, and doesn’t distinguish the two subjects as being different. If you encode it like this, it will allow both “Paris — France” and
“Paris — Texas” . Will this work for you ? — Steve Majewski / UVA
<div class=""><br class="">
</div>
<div class=""><img apple-inline="yes" id="89A941A9-522F-4E37-9261-E02C5654BD0E" height="611" width="933" apple-width="yes" apple-height="yes" src="cid:8FF6B995-F62C-4098-952C-754E9476D30C@zyxel.com" class=""></div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class=""><img apple-inline="yes" id="6AAD81C4-F23F-45D0-93A8-440C59BB2A71" height="611" width="933" apple-width="yes" apple-height="yes" src="cid:FFE8CF28-CD1F-4EEF-8DF7-36CD963C387B@zyxel.com" class=""></div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On Jul 5, 2017, at 1:32 PM, Olivia S Solis <<a href="mailto:livsolis@utexas.edu" class="">livsolis@utexas.edu</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">Hello all,
<div class=""><br class="">
</div>
<div class="">I am not sure how many ASpace users out there share the most recent issue I have encountered migrating data to ArchivesSpace. For a number of reasons, the Briscoe Center has decided to go with GeoNames as our canonical controlled vocabulary for
subject/geographical terms. This is a recent adoption and much of the legacy EAD we use goes with Library of Congress Geographic terms, which we are mapping to GeoNames. We are using Islandora for our digital repository for item-level description. i.e. We're
using the MODS <a href="https://www.loc.gov/standards/mods/userguide/subject.html#hierarchicalgeographic" class="">hierarchicalGeographic</a> element, which works well with GeoNames because GeoNames also uses a hierarchical system to classify its terms. So
for individual MODS records for digital objects you can do something like city: "Paris", country: "France" for one record vs city: "Paris", state: "Texas" in another. There would be two instances of "Paris" in our cities taxonomies, distinguished from each
other by their broader terms and associated URIs. There is no disambiguating information in the labels themselves. The difference between the cities in records is given by the broader state or country elements plus URIs.</div>
<div class=""><br class="">
</div>
<div class="">That works great for item-level description, but causes a number of problems for collection level description in ArchivesSpace. </div>
<div class="">
<ol class="">
<li class="">It appears that ArchivesSpace won't let me create a subject of the same type (e.g. Geographic) from the same source (e.g. GeoNames) that has a label identical to another term classified with the same type/source.</li><li class="">Just for the sake of experimentation in our ASpace sandbox, I identified one of my "Paris" records as a cultural context term. It was difficult to know the difference between the two when I tried to apply the subject to a resource record. The autocomplete
feature did not include any disambiguating information (e.g. from the Scope field or the identifier field in the subject records). The browser headers in the "Browse" subjects link don't include the Scope note either.</li><li class="">Even if I could create two GeoNames geographical subjects with the label "Paris", I'm not sure how to communicate to the ASpace end user the difference between the cities when they are applied to records. I can add notes in the "Scope" field for
each subject record -- "France" and "Texas" -- to communicate the info, but the scope field for the terms doesn't appear in e.g. a resource record's linked subject.</li><li class="">Even if we apply the correct label, the human-readable disambiguating information ("Texas" vs. "France") won't export to our EAD and our end users might get confused about which Paris we mean, especially if there happens to be a collection with
both the Paris in Texas and the Paris in France. In such a case would we include the two different "Paris" subjects plus "France" and "Texas"? Again, this illustrates a difference in item vs. collection-level description. We publish our EAD via a consortial
regional portal hosted by the University of Texas, TARO, which is how researchers view our finding aids online. It's possible we'll open up the public interface, but we're not there yet.</li></ol>
Has anyone else encountered these problems? I'm sure there is a solution/numerous possible solutions to the problems above, though it might mean altering the GeoNames label in ArchivesSpace to include the disambiguating information. Not exactly kosher if we
say we're using GeoNames terms, but we might have to. We want to use the same controlled vocabulary terms regardless of system for global consistency, ease of maintenance etc. I can imagine a kind of customization where our EAD exporter could grab, e.g. the
"Scope" field with the broader term's label and append it to the label for, in this example "Paris", surrounded by parentheses. But that presumes we can enter two different GeoNames/geographical terms "Paris".</div>
<div class=""><br class="">
</div>
<div class="">See screen shots with fake data. FYI, we are on ASpace version 1.5.3.</div>
<div class=""><br class="">
</div>
<div class="">Thanks, and hopefully I'm not the only one with this problem!</div>
<div class=""><br class="">
</div>
<div class="">-Olivia</div>
<div class="">
<div class=""><br class="">
</div>
-- <br class="">
<div class="gmail_signature">
<div dir="ltr" class="">
<div class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div style="font-size:12.8px" class=""><font class="">Olivia Solis, MSIS</font></div>
<div style="font-size:12.8px" class=""><font class="">Metadata Coordinator</font></div>
<div style="font-size:12.8px" class=""><font class="">Dolph Briscoe Center for American History</font></div>
<div style="font-size:12.8px" class=""><font class="">The University of Texas at Austin</font></div>
<div style="font-size:12.8px" class=""><font class="">2300 Red River St. Stop D1100</font></div>
<div style="font-size:12.8px" class=""><font class="">Austin TX, 78712-1426</font></div>
<div style="color:rgb(136,136,136);font-size:12.8px" class=""><span style="font-size: 12.8px;" class="">(512) 232-8013</span></div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<span id="cid:F06ECF83-2DD3-46CC-BDD5-B0712176D6E8@zyxel.com"><Screen Shot 2017-07-05 at 11.35.49 AM.png></span><span id="cid:16D15857-C51A-4477-A60B-B1B6A0A678DE@zyxel.com"><Screen Shot 2017-07-05 at 11.32.47 AM.png></span><span id="cid:47344414-0DD1-4DDF-B65F-FF2480A0CF83@zyxel.com"><Screen
Shot 2017-07-05 at 11.42.54 AM.png></span><span id="cid:B8752228-1A9D-4258-BBC3-C194A4E24CDB@zyxel.com"><Screen Shot 2017-07-05 at 11.42.37 AM.png></span>_______________________________________________<br class="">
Archivesspace_Users_Group mailing list<br class="">
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org" class="">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br class="">
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<br class="">
</div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>