Sending collection metadata to NCBI system
Hi @lathrops1
I don't see these requirements in any other issues, apologies if I've missed it somewhere.
Can you confirm the requirements for when and how to send the collection metadata to NCBI.
My understanding is that there are three use cases:
- For the collection page: NCBI system creates the
<collection-list>
node (as in this example:bookgenallcollect.xml). This corresponds to the NCBI domain service setting (#226)collection-auto-rebuild
which triggers a nightly rebuild of collection lists.- Should the collection metadata in BCMS be sent any time it's updated?
- How should it be sent?
- Book processed at the chapter-level
- Assuming the book belongs to a collection, should collection metadata be sent each time book metadata is sent (as raised in #315 (closed))?
- How should it be sent?
- Book processed at the book-level
- You provided the below in #270 (closed) which I assume only applies to books processed at the book-level
- should the entire
<collection-meta>
node be written into the `book.xml' file?
There are two types of collections in Bookshelf (see data below): (1) A “book-series” that comes from the source / submitter – it corresponds to a publisher’s published series of books or documents/reports (2) A “ncbi-books-collection” that is created by NCBI as a container for all books submitted within it, which may be based on funding OR the accepted book series above – this is internal NCBI metadata not always known by submitter
Both of these need to be contained in the xml. The “ncbi-books-collection” (and maybe also “book-series”) should be copied over from the collection and the collection meta. These and custom meta source type may be copied over into the book meta directly from the collection page, via some kind of rules of clone domains for domains in that collection.
@John.kopanas I'm attaching all other sample collection metadata received: