metadata request

[At_Libitum]

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

[theducks]

Originally Posted by At_Libitum

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

[At_Libitum]

Originally Posted by theducks

Sounds like a good case for a PI.
Map detected optional DC Metadata to PRE-designated Custom fields

Well, actually it seems dc:source is one of the standard fields so I would consider that not a good solution because then you lose the original data as nothing else but Calibre can read Calibre's custom metadata

Of course if dc:source is present in the original it will likely remain present, but if you create an epub from scratch (i.e. metadata going in the other direction) then you have to be aware that custom columns will end up as custom metadata and that you will still need to fill in these 'standard' fields manually if you want to have them contain data.

[kovidgoyal]

I am not going to add another standard column to metadata. You will find that the epub standards committee will go on and on adding "standard" fields to the epub standard, just take a look at epub 3. It is not calibre's mission to map its standard metadata set to epub. calibre existed long before epub and is designed to work with a much larger set of book formats than just epub.

[At_Libitum]

forgive me for giving the impression that it was only epub related. I mentioned the format out of habit because that is what I mostly use. the dc metadata spec is of course not limited to the epub format but a standard of its own.

I also didn't think the format would be of any importance. But I'll have to accept your decision. Which is too bad because source and relation can provide very useful information relating to that publication. having it read automatically would have made life a little easier.

Plugin it is then.