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

First example of feature descriptions via cldf markdown #25

Draft
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

xrotwang
Copy link
Member

No description provided.

@xrotwang
Copy link
Member Author

@MiinaNo I started experimenting with reformatting the feature descriptions using CLDF markdown (see https://github.com/cldf/cldfviz/blob/main/docs/text.md).
This would entail

  • extracting references and examples from the descriptions and adding them to the dataset, i.e. to cldf/sources.bib and cldf/examples.csv
  • re-formatting the descriptions in CLDF markdown

Here's what an example would look like:

What do you think about this? It would add about 50 sources and more than 100 examples to the dataset - which I think would be a nice addition - and should make curation of the descriptions simpler.

@MiinaNo
Copy link
Collaborator

MiinaNo commented Mar 29, 2022

@xrotwang So cool! I even thought that I should contact you an ask about formatting the exampes. This would make everything so much more clear and neat. Let me know if I can somehow be useful. For instance, I have all the references that I used for descriptions in Zotero. I could crate a bib-file as last time? And probably we do not need the separate References part then. This way we could save some space. (I mean that what is at the moment the final section References could finally be deleted as by clicking on the reference one would already see the entire information on the source.)

@xrotwang
Copy link
Member Author

@MiinaNo Yes, when rendered in the web app, the references section could just be skipped. But the nice thing about markdown is that it's also very readable in the static data as hosted by github (see https://github.com/cldf-datasets/uratyp/blob/1340d9e81834a5d73d9d084f6fc1a450446952fd/doc/UT002.md). And there, the references section would probably be good to have.

Regarding the references: I think I managed to extract them all - and also match them with what we already have. See https://github.com/cldf-datasets/uratyp/blob/28aca532910a0ab23d988d175751c74db9d22bee/etc/feature_sources.bib

@MiinaNo
Copy link
Collaborator

MiinaNo commented Mar 29, 2022

@xrotwang Great! References look good. And yes, good point about the static data.

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

Successfully merging this pull request may close these issues.

None yet

2 participants