Opened 14 years ago
Last modified 12 years ago
#642 new feature
new options for List classifier
Reported by: | kjdon | Owned by: | nobody |
---|---|---|---|
Priority: | moderate | Milestone: | Collection building wishlist |
Component: | Collection Building: Classifiers | Severity: | enhancement |
Keywords: | Cc: |
Description (last modified by )
- AZCompactList had -firstvalueonly and -allvalues options.
So, from a list of metadata names, eg dc.Subject,ex.Subject you could choose to use
- just the first available value
- all values of the first metadata element that had values
- all values of all metadata
For List, we don't have these options, and it always uses all values.
Add these (or alternative) options to expand the functionality??
- Add an option "never_bookshelf_last_level" to prevent bookshelfing items with the same metadata value, so that it behaves more like the AZList.
- Check whether List handles section metadata well - can it use multiple metadata for one field
Change History (2)
comment:1 by , 14 years ago
Description: | modified (diff) |
---|
comment:2 by , 12 years ago
Note:
See TracTickets
for help on using tickets.
Diego wrote about this:
I noticed one thing with List classifier. You can specify more than one metadata to use separated with ";" but the case is that the classifier will only use the first one!!!!.
In hierarchy classifier and AZList you have the "allvalues" option that enables you to use all metadata values found, but List seems to be different. This is not the rigth way to work!.