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

What to do with a very specific field from a museum? #19

Open
chin-rcip opened this issue Oct 31, 2019 · 3 comments
Open

What to do with a very specific field from a museum? #19

chin-rcip opened this issue Oct 31, 2019 · 3 comments
Labels
conceptual This issue concerns a more theoretical question Update Documentation Improvements or additions to documentation

Comments

@chin-rcip
Copy link
Owner

Some of the museums having a very specific collection, like the Potato Museum in O'Leary (Prince Edward Island), or the Vancouver Police Museum, in Vancouver (British Columbia).
Those museums may have very specific fields in their database (potato specie, or kind of criminal) that would obviously not be modeled in CHIN Target Model.

The question is: How should we deal with this kind of information? Would it be just not modeled in AC and CiC, or should we add those fields in the model? If we decide to incorporate that specific data, we should have a kind of miscellaneous field that would encompass those fields without having to create different pattern for each cases encountered.

@KarineLeonardBrouillet
Copy link
Collaborator

Maybe we could function like Nomenclature and have a form to submit new fields to be modelled. That way the Vancouver Police Museum, for example, could submit a proposal for a Judicial field to be added to the Life Events category with different types such as accused, accuser, jury, etc. and CHIN could assess whether it is relevant to model it specifically or just create a miscellaneous field. Or we could offer the miscellaneous field, but generate lists of potential fields to add and review them periodically.

@Habennin
Copy link

As I would understand it, as CHIN you don't have to worry about it. It will be difficult enough already to do the integration on the fields that you have decided to do integration on.

You cannot model the whole world

@illip
Copy link
Collaborator

illip commented Nov 24, 2019

+1

During the mapping process, we should keep track of the fields/information that we were not able to handle properly. If it's a frequent field, we might decide to model it.

If it's just a question of vocabularies, I would encourage the museum to work on SKOS vocabularies for their field of expertise.

I don't think a miscellaneous field would be useful...

@illip illip added the conceptual This issue concerns a more theoretical question label Mar 20, 2020
@stephenhart8 stephenhart8 changed the title Issue #19 – What to do with a very specific field from a museum? What to do with a very specific field from a museum? Apr 6, 2020
@illip illip added the Update Documentation Improvements or additions to documentation label Mar 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
conceptual This issue concerns a more theoretical question Update Documentation Improvements or additions to documentation
Projects
Development

No branches or pull requests

4 participants