Closed atiro closed 7 months ago
sounds like an API feature
The first hurdle is that objects and people aren't directly related, there's the Production in between. It would certainly be possible to explicitly include a few works in the Person model via carried_out
to Production
activities which then produced
the objects themselves ... but this seems more like a generic need for "related entities" than explicitly person --> object.
Given that we have a Relationship node to cover arbitrary relationships ... could we have a type of Relationship that is "exemplary object" that could then be pulled out of the person record?
I would opt for Rob's option 1 with using a new E55 Type
. It seems to me that this a typical categorical statement about the object. I.e. we make a group of objects produced by an artist which we consider typical (they are not typical on their own). There is nothing inherent in the relationship between the object and the artist apart from the link via production, so creating a new relationship is not necessary, in my view.
Could we widen the use case to be about concepts/movements?
Because of the contextual nature of the data (plus the brief conversation we had showed how many different use cases and forms it could take, as well as factors like institutional perspective, illustrative images changing over time, etc...) should this part of the model be more recommendation rather than prescriptive? "...more like guidelines rather than actual rules"--Barbossa from Pirates of the Caribbean
Although I love the Pirates quote, I think that if the model does not require the rationale/motivation for designating representative objects/spaces/people, then the groups constituted might only be of use to whoever creates them. The result to me would be a little bit like coming across a highlighted portion of text in a book without notes in the margin: this group/excerpt is important to someone but I am not privy to the reason.
Call on 2020-03-25:
George suggests Attribute Assignment.
Artist - assigned_to_by AttribAssign assigned Set ; Set has_member (object, object, object) ;
Attrib Assign classified_as (exemplary-ness) a E55 Type
Attrib Assign carried_out_by
Another use case from Joe Padfield - highlights for a collection.
As long as the carried_out_by
, timespan
and motivation
are clearly optional, this attribute assignment seems a good option to explore for now!
Note (in case it's not clear from the above) that this use case is NOT the use case of "images that depict the artist", or "images that depict this place" which we can easily model using represents
.
Since sets are represented by their own URIs, this seems like it would limit the size of the artist response. It might also be helpful to aggregators in collecting various sets associated with the artist, each of which might be for a different purpose. I'm sure there are many other use cases this model could be used for where sets of entities have a relationship with an entity or another set of entities.
Need to find a vocabulary term to classify the Set. I can't find anything in AAT (at least) that would be useful for "examples" other than the horribly confusing specimens.
API wise ... should the set be embedded, as for /this/ use case, it will only ever be 1:1 with the resource? (related to #411) Still no AAT term that I can find... should ask Patricia for one. Docs pointer: https://docs.google.com/document/d/1v80kuVwSkdw3hY5uuhN9uhRYGafN3DKjtnYSg4RN8rc/edit
For terms, would this work?
common (extent designation) (multidisciplinary concepts, Associated Concepts (hierarchy name)) Note: Characteristic of belonging equally to more than one, of being possessed or shared alike by all or most of the people or things in question. An example of usage is in indexing groups of works or complex works, for subject or material terms that apply to all items in the group or all aspects of a work that has multiple aspects.
(Being: http://vocab.getty.edu/aat/300404448)
The set has common items (in that they all are exemplary of the artist) but I don't think it implies the original use case of "these are the works the artist is known for, or are good examples of her work"?
As far as embedding core entities, on a recent call, I think someone suggested that entities should be embeddable to avoid having to mint a URI solely for the purpose of creating a reference that appears once in the graph.
So, maybe it makes sense to allow core entities to be optionally embedded only when no URI is minted for that entity. If the data for the entity is duplicated in the graph, should we care or otherwise take a position on that?
Done
AAT concept "samples" for now?
https://vocab.getty.edu/aat/300028875
Note: A sample is a part of anything taken or presented for inspection or shown as evidence of the quality or composition of the whole. For instances that represent a class, use "specimens."
Agreed, good find
It would be useful if we could attach a subset of objects to an artist for use in illustrating them (i.e. known for), rather than having to show all of their works (or picking at random).