Hi, I may be missing something obvious, but is there a way to add mulptiple creators to an image? I am cataloguing a project where I would like to be able to add multiple creators (ie two artists) but have them recorded as distinct entities (for when metadata is exported). Is there a way to do this? Other programs often allow comma separated, or similar,for adding multiple authors for example.
Thanks!
You’re not missing something obvious. Right now the only way to do it is to add a new metadata field, distinct from any that currently exist in the template (e.g., contributor). You can do that template-wide, or you can add a new field to just the one item you’re working on. This is by no means an ideal solution; we’re working on fixing this problem.
Thanks! I would definitely love this as a feature, but the add new field (which I hadn;t discovered) should be a decent workaround at the moment. Thanks again.
Just bumping this to say that I think this would be a really helpful feature to have. I am in the process of cataloging tons of photos and I am unsure whether it would be better to tag multiple creators or add a new field… having multiple creators (a la Zotero) would be ideal, I think.
I’m bumping this again, from several years ago. Have more recent versions added the capacity to enter multiple authors, contributors, etc.? Or is the best practice here to record multiple contributors in notes or as tags?
The data model has not been changed yet. You can use different properties, e.g. dc:creator and dc:contributor for different roles, but currently you can only add each property once. As a workaround you could also add multiple names into a field (or in a note). Using person tags is also an option, I’d say it depends on your project and workflow what is more practical.
Using tags for each person would result in hundreds, maybe thousands of tags, which would then detract from the usefulness of tags. For a single co-author dc:contributor looks best. For longer lists of names I’m leaning toward creating an additional field to contain the lists as a semicolon-delimited text string, which might make it easier to disaggregate the list down the road, if that becomes a need. Does that make sense?
Yes that sounds like a good approach. Especially using semicolons should make it easy to split up the names in post-processing or when upgrading later on.