[Archivesspace_Users_Group] Dual Language Data

[Christine Di Bella]

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.) 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<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[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://github.com/archivesspace/archivesspace/tree/master/common/schemas> 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://www.tei-c.org/release/doc/tei-p5-doc/en/html/MS.html>.)

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<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/20191115/0b44b2e5/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 6608 bytes
Desc: image003.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20191115/0b44b2e5/attachment.jpg>