|
If I understand the question, then the answer is still 'no'. The destination library must have the custom columns before you do the copy. Copying/moving a book will not create them.
There isn't any straightforward way to clone one library's custom column configuration onto another. There are non-straightforward ways, such by library cloning (messing with the metadata.db file) and using the new recovery mechanisms. All of them can easily destroy a library, so I don't want to get into too many details.
|