search

hiscom / hispid

HISPID Terms
6 stars 1 forks source link

Artist field #65

Closed acvaughan closed 8 years ago

acvaughan commented 9 years ago

We will be delivering images of artworks of specimens, and will need to deliver both photographer and artist.

nielsklazenga commented 9 years ago

The record is for the digital resource, not the physical object (artwork), so dcterms:creator is the photographer. The artist can be in dcterms:description and ac:caption and/or there can be a reference to the artwork that was the source of the image via dc:source or dcterms:source.

The Dublin Core definition of dc:creator is 'An entity primarily responsible for making the resource'. Audubon Core doesn't add anything to that. In most cases I would have no problem with giving the artist as the creator as well, but I would prefer to have the photographer or the institution where the photograph was taken as the creator and have the artist in the reference to the source object. Just adding an 'artist' field is apparently very confusing to the punters. We have it in our enterprise image database and it has led to endless discussions as to what goes into which field and quite a mess in the database.

AaronWilton commented 9 years ago

I agree

afuchs1 commented 9 years ago

Also agree Niels.

ben3000 commented 9 years ago

Yep, I agree too.

nielsklazenga commented 9 years ago

There is actually a creator {Artwork or Object detail} element in the new IPTC metadata standard (version 1.2; http://www.iptc.org/std/photometadata/specification/IPTC-PhotoMetadata), which we can use for this. The XMP implementation is Iptc4XmpExt:AOCreator. The Iptc4XmpExt namespace is already used in Audubon Core.

In the new edition of the IPTC metadata standard extra properties have been added to the 'Artwork or Object in the Image structure' (I've got this from the summary; I don't know it because I know the different versions of IPTC so well), so apart from the creator, it also allows for rights data, more detailed descriptions, approximate dates of creation, style period, etc. (for the artwork).

The Artwork or Object in the Image extension resolves the initial issue I had with not being able to distinguish between the digital resource and the physical object that is the source. I don't think we need to add AOCreator to HISPID, but if there is a need to deliver the information, this is the element we should use.