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

Allow vocabs used to have non-unique titles, and to supply alternative titles #178

Open
wu-lee opened this issue Feb 22, 2023 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@wu-lee
Copy link
Contributor

wu-lee commented Feb 22, 2023

No description provided.

@wu-lee wu-lee added the bug Something isn't working label Feb 22, 2023
@ColmDC
Copy link
Contributor

ColmDC commented Feb 22, 2023

Just confirming that this is needed to support text search when we have fields in the data with vocabs that have the same titles, but are in fact different

it is also needed where combined vocabs are use like when combining Primary and Secondary Activities in a filter option.

@wu-lee
Copy link
Contributor Author

wu-lee commented Mar 6, 2023

Yes, that's correct.

Also, an alternative title would also be needed if a vocabulary's default title was not appropriate in the particular context of a map, even though the vocabulary terms were. For example, what the ICA calls "Typology" is called "Base Membership Type" in the ESSGLOBAL definitions.

@ColmDC
Copy link
Contributor

ColmDC commented Apr 26, 2023

How much effort is required to finish supporting this?

@wu-lee
Copy link
Contributor Author

wu-lee commented May 15, 2023

I think it depends on - or is closely related to #199

My best idea of implementing it is to allow vocabs to be used as generic and localised ID-naming tables, then having titles for fields and vocabs to be looked up from them. It would need inventing a way to decide which vocab to look up in. Perhaps there could be a convention that a certain vocab is always used to look up vocab and/or field names, and fall-back is the names (or identifiers) used now?

The problem with estimation of effort, is that part of of the effort is coming up with a workable scheme, which I think boils down to taking the time to do an experiment. So it seems more like a question of, how much time do we want to allocate to an experiment, and when do we start?

Maybe allocating half or a whole day's worth would get some answers, if not solve everything.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants