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

Custom tags #197

Open
AnnaLuisaD opened this issue Jun 29, 2022 · 4 comments
Open

Custom tags #197

AnnaLuisaD opened this issue Jun 29, 2022 · 4 comments
Assignees

Comments

@AnnaLuisaD
Copy link
Collaborator

I don't have this idea fully fleshed out, but multiple dictionary managers have requested the ability to make their own custom tags. So they could:

  1. create a tag (so you would need a "create a tag" button)
  2. customize it to have it be called what they want
  3. the ability to tag entries with this tag
  4. it would show up in the right sidebar and you could filter by it (Diego says this step might be complicated)

I will try to add more details as I think this through.

@AnnaLuisaD AnnaLuisaD moved this to Request for Comments in Development Roadmap Jun 30, 2022
@jacob-8 jacob-8 self-assigned this Aug 24, 2022
@jacob-8 jacob-8 changed the title Custom "tag" functionality in right sidebar Custom tags Aug 24, 2022
@Danble
Copy link
Collaborator

Danble commented Oct 7, 2022

I was thinking about this and my proposal is to add a new entry field in the entry.interface.ts file called: ct that stands for custom tags.

In our database this new field should be an array of documents: these new documents should have two keys: name and value name will be the custom tag name users want to call it and the value can be filled later on the normal entry view editor.

Example:
ct = [ { title: "my own custom tag", value: "" }, { title: "another custom tag", value: "example value" } ]

I'm just wondering if algolia can allow us to filter by those key names @jacob-8
I think it is possible

@Danble Danble moved this from Request for Comments to Preparing in Development Roadmap Jan 11, 2023
@AnnaLuisaD
Copy link
Collaborator Author

Greg is concerned that this category is too random and that there is no super-ordinate category. The types of requests that we have received about custom tags are:

  • linguists wanting new semantic tags that are relevant to the language (such as "parts")
  • needing to tag entries temporarily so that other people can edit them later (for example "needs revision" or "archaic term"); this is a form of starring them for internal editing
  • linguists want to be able to add other categories that are not quite parts of speech or semantic domains, such as "proverbial expressions" or "slang" or "insults" etc

@AnnaLuisaD
Copy link
Collaborator Author

Anna's feedback and thoughts. I would like to use custom tags for my internal workflow on the platform:

  • I can tag certain entries for collaborators to work on, such as fixing scripts, adding notes, adding example sentences. these tags would be temporary and don't necessary need to be in public view
  • we need a "star" that could be used. I was thinking custom tags sort of replaces the need for a star.
  • I would use custom tags to add an "Archaic" tag to the Ishir content, since there are a lot of terms that are archaic and are no longer in use in the community. Greg was saying maybe that would be beneficial for the public to see
  • for Pacific northwest languages, they do need a tag like "basketry" that we don't have on our list
  • some linguists have parts of speech that are used in their local traditions (such as in the Mayan languages: they have a list of certain parts of speech that are not commonly used outside of Mayan linguistics, so they are not in our main list)
  • Diego is thinking maybe we create at least two types of custom tags (internal use only, some for public viewing?)
  • Greg is thinking maybe we just call them "Custom Semantic Domains" (that would be helpful for Fede, Pam, Chris B, Peter C., Spike, etc)

@AnnaLuisaD
Copy link
Collaborator Author

In terms of Archaisms, Greg is saying it is connected to semantics. For example, the word "silly" used to mean "holy" but it has lost that sense. Another example is that "hussy" used to mean "housewife" but now it has a pejorative meaning that is not connected to housewife.

One glaring area that we have no data field for is related to Etymology of the words. Archaisms would not necessarily fall into this category. I think "Linguistic History" is an accessible term (rather than Diachrony) as a data field that people could type in. In terms of coding, it would just like the Notes field

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Preparing
Development

No branches or pull requests

3 participants