VGT records

[VincentCCL]

VGT records should also have Flemish Sign Language and Vlaamse Gebarentaal as their languages, so they can be found when looking by language selection

[kreetrapper]

As far as I can see, all VGT entries have "Flemish Sign Language (VGT)" listed as a language. I would not like to list the same language in multiple ways (e.g. also listing "Vlaamse Gebarentaal" as you suggest). We are planning to switch to using ISO-codes (instead of language names) which, I think, would solve this issue.

[VincentCCL]

As far as I know now this is treated inconsistently. When looking for Flemish Sign Language I get one hit. When searching for VGT (in the general task bar), I get at least three hits which I don't get otherwise. While ISO codes may solve the problem in the background, these ISO codes for sign languages are very uncommon and not used by the sign language communities, so they should be converted to human-readable forms. Cf. https://vlo.clarin.eu/?1&q=vgt

[kreetrapper]

Just to avoid confusion. Are you talking about the Sign Language Resource Family (as implied by the issue being in this git repo) or about the VLO? My comment was only about the Resource Family. While the Families are curated by us, the VLO is fed from all the various CLARIN centres and the inconsistency is mostly due to these very heterogeneous sources.

[VincentCCL]

I was talking about the VLO. Apologies.

kind regards,

v.

On 30/06/2023 10:18, alekoe wrote:

Just to avoid confusion. Are you talking about the Sign Language Resource Family (as implied by the issue being in this git repo) or about the VLO? My comment was only about the Resource Family. While the Families are curated by us, the VLO is fed from all the various CLARIN centres and the inconsistency is mostly due to these very heterogeneous sources.

-- Reply to this email directly, view it on GitHub [1], or unsubscribe [2]. You are receiving this because you authored the thread.Message ID: @.> [ { @.": "http://schema.org", @.": "EmailMessage", "potentialAction": { @.": "ViewAction", "target": "https://github.com/clarin-eric/resource-families-issues/issues/412#issuecomment-1614302431", "url": "https://github.com/clarin-eric/resource-families-issues/issues/412#issuecomment-1614302431", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { @.***": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

Links:

[1] https://github.com/clarin-eric/resource-families-issues/issues/412#issuecomment-1614302431 [2] https://github.com/notifications/unsubscribe-auth/AIEEDJP5QXO2JZDOMAWZGDTXN2DURANCNFSM6AAAAAAZYOGOVY

[twagoo]

Thanks @VincentCCL for reporting this! As this issue relates not to the resource families directly but rather to (a lack of) harmonisation in the metadata across centres, the information should probably be "rerouted" - and this issue closed.

I'll leave the closing of the issue up to @kreetrapper but before that let me summarise my interpretation of the situation for the record.

Among the search results for vgt in the VLO, we currently have

• 4 records from INT
• 17 records from MPI-PL

... as well as 1 record from another provider that is not related to Flemish Sign Language at all (also not represented as such, so not an issue in terms of this query).

Out of the 21 'actual' matches, 5 records use the language code 'VGT'.

The remaining records include:

• 1 record from INT ("Hotel Review Corpus in Nederlandse Gebarentaal")
• 15 records from the MPI

I'll get in touch with the providers, as these all look like issues that can and should be addressed on their end.

Hope this helps!

P.S. this makes me realise that we need to find a new platform to document and trace metadata issues, now that our Trac system has been deprecated.