Customisable field for the name of an item


#1

Hi
We created items for persons and other kind of ressources that don’t have a “title” in proper sense. But we had to add a dc:title to our model, in order to display the “name” of the ressource, in admin and public view.
It is a bad habit, and we would have prefer to use a skos:label for example (we also have this property of course).
Is someone working to make the field used for the name of the ressource more customisable ? As Omeka S is more flexible than Omeka Classic regarding the data model, the system should give the ability to admins to define any property as the “name” of the ressource.


Using Item Property from a vocabulary other than Dublin Core, problem in item-set-browse and item-display pages
#2

We tackled this problem from a different direction, letting you pick within a site what property is used for the “title” and “description” areas… but of course that requires you to use something consistent within a site.

I’ve thought before about what you’re proposing, basically allowing resources to mark which property is their “title,” and it makes some sense. And quite possibly a good bit more sense than what we’ve actually done already.


#3

Within our site we will have different kind of items (documents, authors, places…), so I don’t think your solution will satisfy us :confused:


#4

No answer at hand, but a few questions, maybe to clarify.

It is all about setting a property from a vocabulary other than Dublin Core to be used for the “title” and “description” areas in item-set and item browse and display pages .

This choice could be made on different levels:
a) A site-wide setting would not be satisfying if a user intends to work with multiple vocabularies within one site.
b) A setting for each ressource seems to me pretty much work on the user side and against the idea of standardization.
c) So could it be possible to make this choice on the vocabulary level?


#5

Hi
Why not at vocabulary level, but a user builds a template using different properties from different vocabularies, it can end up as a mess…
But each ressources needs to be linked to a ressource template. So the more logical for me would be to manage the “displayed name” at ressource template level.

M. Saby


#6

That’s what we’ve been thinking: that this would be a new setting for resource templates.