[Archivesspace_Users_Group] Dual Language Data

Thu Nov 21 00:53:28 EST 2019

Hi Christine,

At our end, it is only aspirational at this point, but I would like
(someday) to eventually have a bilingual finding aid portal that includes
Arabic, and that could describe our Arabic content in that language.  The
last two archival repositories that I worked at (in the U.S.) also had
significant amounts of non-English materials, including Russian, that would
have benefited from description in those languages/scripts and software
that would better support that.

Best,

Brad Bauer
New York University Abu Dhabi

On Wed, Nov 20, 2019 at 7:25 PM Noah Huffman <noah.huffman at duke.edu> wrote:

> Hi Christine,
>
> Chiming in late to this, but this would be extremely valuable in our
> context. We are increasingly doing multi-lingual description and modeling
> this data in ArchivesSpace has been a bit of a challenge so far. For notes,
> we record each language in a separate note subrecord (works OK), but for
> titles our workaround has been to add an additional note subrecord on the
> Archival Object with a label like “Title (Chinese).”  Occasionally, we’ve
> just crammed both languages into the same title field separated with pipe
> characters (not my favorite approach).
>
> Ultimately, as Scott suggested, we’d love some sort of togglable front-end
> where a user could select their preferred display language.  Or, languages
> could be displayed based on a user’s browser language setting. EAD3 has
> some facility for handling multi-lingual description, but ASpace EAD3
> exports can’t really take advantage of this.
>
> Here are links to some of our published multilingual finding aids just to
> give you a sense of the variety of multi-lingual description. We manage
> this description in ArchivesSpace, but don’t currently use the
> ArchivesSpace public interface.
>
> Radio Haiti (collection description in English, French, Creole):
> https://library.duke.edu/rubenstein/findingaids/radiohaiti/
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__library.duke.edu_rubenstein_findingaids_radiohaiti_&d=DwMFAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=8Xy72keGxrm5-LXMewd02A&m=f6J_qE6HACr-AS4eXsitlWcNNvIkOaBQfpDZuqC6yVc&s=QA2sONiOkf7MFNJWhOAasu-qs5yWTYLvBmwRCVnD9rI&e=>
>
> Heschel (collection description in English, Hebrew):
> https://library.duke.edu/rubenstein/findingaids/heschelabraham/
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__library.duke.edu_rubenstein_findingaids_heschelabraham_&d=DwMFAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=8Xy72keGxrm5-LXMewd02A&m=f6J_qE6HACr-AS4eXsitlWcNNvIkOaBQfpDZuqC6yVc&s=GoDNwNHWj4UzQJ_eputYUuKPAFD6MQvNlTNDt5YIdWY&e=>
>
> Shockley (item-level photos described in English and Chinese):
> https://library.duke.edu/rubenstein/findingaids/shockleywilliamh/
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__library.duke.edu_rubenstein_findingaids_shockleywilliamh_&d=DwMFAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=8Xy72keGxrm5-LXMewd02A&m=f6J_qE6HACr-AS4eXsitlWcNNvIkOaBQfpDZuqC6yVc&s=6qlZK5AR1r55TgGnrVkj_ZVnnCHaP9sQxaFFVRJhdGY&e=>
>
> -Noah
>
>
>
> ================
>
> Noah Huffman
>
> Archivist for Metadata, Systems, and Digital Records
>
> David M. Rubenstein Rare Book & Manuscript Library
>
> Duke University | 919-660-5982
>
> http://library.duke.edu/rubenstein/
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__library.duke.edu_rubenstein_&d=DwMFAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=8Xy72keGxrm5-LXMewd02A&m=f6J_qE6HACr-AS4eXsitlWcNNvIkOaBQfpDZuqC6yVc&s=-28JTTWyd7RHGLrsNRr8Anb9mJRwpjODxu-vdjbt4ZU&e=>
>
>
>
>
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org <
> archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Christine
> Di Bella
> *Sent:* Friday, November 15, 2019 11:13 AM
> *To:* Archivesspace Users Group <
> archivesspace_users_group at lyralists.lyrasis.org>
> *Subject:* Re: [Archivesspace_Users_Group] Dual Language Data
>
>
>
> Hi all,
>
>
>
> I’m very interested in discussion of the underlying issues as well as
> whether people have done anything to work around ArchivesSpace’s
> limitations in this area. (I’m fact, I recently created a Jira ticket for
> something in this area based on other inquiries:
> https://archivesspace.atlassian.net/browse/ANW-957
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_ANW-2D957&d=DwMFAg&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=F0JE8U9-xhxe_nE7d7aEUi-uqfKqvYJ222bS0oz9mko&m=aMIF32xjFuNMLKOiZ0UlXNaCfVPs3mwVN5fVQmHZOq0&s=cnNHeIkbJRrRCjCkAuEdvSYHTO9vm-YoBMkSRLJlZIQ&e=>.)
> As I mention in that ticket, because of the repeatability of sub-records
> doing description in multiple languages is possible in some areas of
> ArchivesSpace but not all, and there is not way for our current EAD exports
> (either EAD2002 or EAD3) or other outputs to distinguish between the
> different languages. How many of you work in contexts where this would be
> valuable (or even required) for individual collections, to work with
> different service populations or for your local or national context?
>
>
>
> Christine
>
>
>
> Christine Di Bella
>
> ArchivesSpace Program Manager
>
> christine.dibella at lyrasis.org
>
> 800.999.8558 x2905
>
> 678-235-2905
>
> cdibella13 (Skype)
>
>
>
> [image: ASpaceOrgHomeMedium]
>
>
>
>
>
>
> ------------------------------
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org <
> archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of
> Andrew Morrison <andrew.morrison at bodleian.ox.ac.uk>
> *Sent:* Friday, November 15, 2019 10:24:34 AM
> *To:* Archivesspace Users Group <
> archivesspace_users_group at lyralists.lyrasis.org>
> *Subject:* Re: [Archivesspace_Users_Group] Dual Language Data
>
>
>
> I would imagine it would require a major overhaul or fork of ArchivesSpace
> to make it capable of capturing two or more translations of everything in a
> single record. The data model
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_archivesspace_archivesspace_tree_master_common_schemas&d=DwMFAg&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=F0JE8U9-xhxe_nE7d7aEUi-uqfKqvYJ222bS0oz9mko&m=aMIF32xjFuNMLKOiZ0UlXNaCfVPs3mwVN5fVQmHZOq0&s=TG5UzSFotFC2wJfEivQ1QbNikE1XTTAj4cYtcbmKR4A&e=>
> is close to the EAD 2002 schema, which isn't multilingual in this sense
> (unlike, say, the manuscript description module of the TEI schema
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.tei-2Dc.org_release_doc_tei-2Dp5-2Ddoc_en_html_MS.html&d=DwMFAg&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=F0JE8U9-xhxe_nE7d7aEUi-uqfKqvYJ222bS0oz9mko&m=aMIF32xjFuNMLKOiZ0UlXNaCfVPs3mwVN5fVQmHZOq0&s=Xrz9ORVm6mx5TzauJKunMBVqSbZyvQ-uxOIYMl2edbE&e=>
> .)
>
>
>
> Andrew.
>
>
>
>
>
> On Fri, 2019-11-15 at 12:30 +0000, RENTON Scott wrote:
>
> Hi folks
>
>
>
> Wondering if anyone can help with a challenge I've been set. I've got a
> task to investigate how easily we could populate a togglable
> English-Scottish Gaelic front end supplied by Archives Space data (through
> either the SOLR index or the API- we've built a few single-language sites
> which interrogate ArchivesSpace SOLR).
>
>
>
> I know that language can be captured when cataloguing, but would I be
> right in saying there is no way of capturing the same data in multiple
> languages (i.e. can I catalogue a title for a resource twice, once in
> English, and once in Gaelic, and would the link, that they are 'the same
> thing' be preserved?)?
>
>
>
> The current website is a bespoke postgres db, which can do this. We want
> to migrate the users over to ArchivesSpace, and I'm pretty sure it can
> handle everything, but this would be a sticking point if it's not possible.
>
>
>
> Cheers
>
> Scott
>
>
>
>
>
> ==========
>
> Scott Renton
>
> Library Digital Development
>
> Floor F East
>
> Argyle House
>
> 515219
>
> The University of Edinburgh is a charitable body, registered in Scotland,
> with registration number SC005336.
>
> _______________________________________________
>
> Archivesspace_Users_Group mailing list
>
> Archivesspace_Users_Group at lyralists.lyrasis.org
>
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group <https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwMFAg&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=F0JE8U9-xhxe_nE7d7aEUi-uqfKqvYJ222bS0oz9mko&m=aMIF32xjFuNMLKOiZ0UlXNaCfVPs3mwVN5fVQmHZOq0&s=HekT5fesx8g1YAJlyvSQHFCnDP0KC5d_Lse4uUn6U-Y&e=>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
>
> https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwICAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=8Xy72keGxrm5-LXMewd02A&m=f6J_qE6HACr-AS4eXsitlWcNNvIkOaBQfpDZuqC6yVc&s=IVl54tEQCokSJ2anGzyw5YNaewFPnZN4IkFvjdcDYRs&e=
>

-- 
Brad Bauer
Librarian for Archives and Special Collections
New York University Abu Dhabi
PO Box 129188
Saadiyat Island
Abu Dhabi, UAE
e-mail:  bdb3 at nyu.edu
phone:  +971 2 628 7335
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20191121/084d3ec9/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 4017 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20191121/084d3ec9/attachment.jpg>