Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple numeric identifiers for same concept #22

Closed
shash42 opened this issue May 22, 2021 · 6 comments
Closed

Multiple numeric identifiers for same concept #22

shash42 opened this issue May 22, 2021 · 6 comments

Comments

@shash42
Copy link

shash42 commented May 22, 2021

In the sqlite database that is obtained after the CLICS install, what seems to be the same concept (parameter) is represented multiple times with different numeric identifiers. For example, consider the types for Friday:
478_friday
993_friday
218_friday
350_friday

Is there a reason that such a distinction is made? What leads to the classification? Or is it safe to collapse these multiple parameters into a single concept? Some documentation would really help this in regard, especially to weed out potential mistakes in future research using CLICS3.

@LinguList
Copy link
Contributor

This is not unexpected, since CLICS3 is based on different datasets coded in CLDF, with their own internal IDs. What unifies them is the column "Concepticon_ID" and "Concepticon_Gloss":

sqlite> select ID, Name, Concepticon_ID, Concepticon_Gloss from ParameterTable where ID like "%_friday";
350_friday|Friday|1692|FRIDAY
478_friday|Friday|1692|FRIDAY
993_friday|Friday|1692|FRIDAY
218_friday||1692|FRIDAY

@LinguList
Copy link
Contributor

The network approach in CLICS makes use of the Concepticon_ID where present, so there is no error.

@LinguList
Copy link
Contributor

As to documentation: this is handled in our documentation for the CLDF format in general, and you find documentation and additional information at the CLDF website at https://cldf.clld.org, with further links, and we also regularly discuss certain aspects of CLDF in our blog at https://calc.hypotheses.org.

@LinguList
Copy link
Contributor

@xrotwang, as I consider this an issue that is sufficiently discussed in all CLDF-accompanying resources, I'd suggest to close this issue?

@shash42
Copy link
Author

shash42 commented May 22, 2021

Thank you so much for the prompt response and detailed resources!

@chrzyki
Copy link
Contributor

chrzyki commented May 26, 2021

Thanks for explaining this, @LinguList. @shash42 feel free to ask more questions if you need additional help/guidance.

@chrzyki chrzyki closed this as completed May 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants