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

Include guidelines in menu #547

Open
nichtich opened this issue Mar 30, 2020 · 2 comments
Open

Include guidelines in menu #547

nichtich opened this issue Mar 30, 2020 · 2 comments
Labels
user experience Usage should be fun and easy

Comments

@nichtich
Copy link
Member

nichtich commented Mar 30, 2020

Add a "guidelines" ("Richtlinien") entry to the menu with a link to general guidelines and a list of guidelines for configured combinations of vocabularies (and/or selected source/target vocabularies).

The configuration format could be extended to make fromScheme and targetScheme optional:

{
   "guidelines": [
    { "url": "http://link.to/general-guidelines" },
    { "fromScheme": { "uri": "http://bartoc.org/en/node/1940" },
      "prefLabel": { "en": "Mapping from Wikidata" }, "url": "..." }
    { ... },
  ]
}

Selecting a guideline would also select the given combination of fromScheme / toScheme, so this feature is also useful to provide a list of vocabulary-combinations to look at.

@nichtich nichtich added the user experience Usage should be fun and easy label Mar 30, 2020
@nichtich
Copy link
Member Author

We have this shown with an icon in the MappingEditor but a list of guidelines should be shown in ConceptDetail. Inject the guidelines as field subjectOf of the concept scheme in fromScheme. Then show it in ConceptDetail with title "mapping guideline" as default.

@nichtich nichtich added this to the 1.6.0 milestone Dec 10, 2021
@stefandesu
Copy link
Member

I think you need to clarify this.

  1. Why the need to inject the guidelines? Where do the guidelines come from? if they are configured or hardcoded, we can use that data directly. Or do you mean they will be part of BARTOC, so the data will come from the API?
  2. Why only fromScheme? It feels like mapping TO a vocabulary is just as important or even more important.
  3. Where would the "mapping guideline" in ConceptDetail be placed exactly? I still feel like MappingEditor would be a better place.
  4. How would we deal with guidelines that specify how to map one specific vocabulary to another specific vocabulary, like RVK-BK? In this case, it would also make more sense to show it in MappingEditor, I think.

@stefandesu stefandesu modified the milestones: 1.7.0, 1.8.0 Apr 14, 2022
@nichtich nichtich removed this from the 1.10.0 milestone Jun 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
user experience Usage should be fun and easy
Projects
None yet
Development

No branches or pull requests

2 participants