#Tortoisehg set bundle compression type archive#
#Tortoisehg set bundle compression type software#

Linguists (especially American linguists) are trained deconstructionists. Since there can be multiple derivative products per lexical data set, in a DSpace architecture, it seems that both objects should be items with a relationship 'is_derivative_of' So, a dictionary item is_derivative_of the lexical data set item.

#Tortoisehg set bundle compression type archive#

That is, on the back end of the service to archive resources, the archive record's architecture and organization needs to reflect the derivative product relationships. With respect to the distinction between a lexical data set and an out-put end product like a 'dictionary', the distinction must also be clear in the archiving records.

Therefore, the SIL services which deal with Lexical data must be clear, persuasive and educational in their communications. While it would be ideal to flip a switch and change these 'linguist's' orientation, such a switch does not readily present itself. From such a source multiple end products can be produced. It has been well argued (by Steve Echerd, Gary Simons and others) that SIL would rather see their staff oriented towards 'the lexical database' because that is the source. The archive's (and LSDev too) audience (linguists) often think in terms of 'the dictionary' or 'the wordlist'. (Because these strategies are dependent on the data formats and the file types and the data resource types.) The longevity (Data maintenance strategy) and upgrading of data formats. Marketing of products (on the behalf of linguists and economic partners, including the matching of resources to SIL's services).Ĭommunication between submitters and archivists.Įffective matching of metadata to other metadata systems. Why do we need a typology of resource types? It is important to have this conversation so that as archivists and as linguists (submitters) we know where in the spectrum of lexical resources FLEx and Toolbox data sets fit. For instance communicating to linguists what it means to archivists to archive a lexical resource, and communicating to data wranglers what resources are in the archive and how they are constructed. It is an active act of translation to communicate the semantics, concepts and implications from one community to another community. Linguists, archivists, and data wranglers all think in different terms (worldviews). Therefore I want to look for a moment at the dichotomy of lexical resourceses. or texts.hile I suggest that FLEx databases are more than just dictionaries in database formats, a lot of the questions I have encountered from SIL users of FLEx who are looking to archive FLEx databases, have related to FLEx as a lexical resource.

So when we talk about archiving FLEx we need to talk about it broadly as if the FLEx user was using it to store words, texts and relationships about words, and relationships about words in texts, and audio files and video files, and photos and the relationships of those media to the words.

Others use FLEx to generate dictionaries, yet others use it to store texts as if were the final location those texts belonged. Some people only use the parsig feature to parse texts.

#Tortoisehg set bundle compression type software#

That is some use the software to maintain a list of words in the language being studied. What is being archived?įLEx is many things to many people. The following discussion provides a road map and the dicsussion of all three elements listed above. Mostly because finding seekers are seeking to meet the requirements of institutions offering funding. The academic discussion around these three things is all over the map. What is does it mean to 'archive' as a process of activity.Any discussion about archiving needs to set out three things: