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

Issue #20 – What to do with the “Remarks” field in some museums? #20

Closed
chin-rcip opened this issue Oct 31, 2019 · 6 comments
Closed

Comments

@chin-rcip
Copy link
Owner

chin-rcip commented Oct 31, 2019

Most of the museum dataset have a kind of miscellaneous field, often called "remarks" that contains some various information that could not be documented elsewhere in their dataset (this is the case in Artist in Canada). This kind of field contains various kind of information and is therefore not consistent.
What should CHIN do with this kind of information? Should CHIN create a "remark" field?

@KarineLeonardBrouillet
Copy link
Collaborator

Yes it would be useful especially if we consider text mining some of these description in the future to extract more data.

@Habennin
Copy link

There is already a pattern for that in your modelling. I mean you can use the

E73 -> p 190 -> Literal
E73 -> p2 has type ->E55 'Curatorial Note'
E73 -> p2 has type -> E55 'Curatorial Note' - > p2 ->E55 Description
E73 -> p94i -> E65 -> p14 ->E39

pattern in order to model this. Chin could coin its own uri for 'curatorial note' but I think AAT is also doing this for linked.art.

@stephenhart8
Copy link
Collaborator

This "Curatorial Note" pattern has been added to the TM 2.0 and will be tested in the following month.
I propose to close this issue.

@Habennin
Copy link

+1 to closing

@illip
Copy link
Collaborator

illip commented Mar 20, 2020

@stephenhart8 +1 to closing!

@stephenhart8
Copy link
Collaborator

By general agreement, I close this issue.

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

No branches or pull requests

5 participants