View Single Post
Old 10-16-2013, 11:24 AM   #2
theducks
Well trained by Cats
theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.
 
theducks's Avatar
 
Posts: 31,210
Karma: 60406678
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
Quote:
Originally Posted by At_Libitum View Post
Got a request.

As a result of my recent exposure to plugin internals and metadata I noticed that there is a standard metadata field dc:source

According to the documentation this field is intended to hold a reference to the source the book was based on (or derived from)

I would very much like to see this field be automatically read and present as option in the library columns when adding a book to the library. I was already using a custom column for same which I always need to update manually , but it would be ever so much easier if the original dc:source got used instead (didn't even know it existed)

Seems a bit double, me adding a custom column for metadata for something that is already present in the standard metadata fields
Sounds like a good case for a PI.
Map detected optional DC Metadata to PRE-designated Custom fields
theducks is offline   Reply With Quote