...
Switch → General → Content_Processing → Production → JRNL_Resupply Issue_Resupply_JATS
Twice a week this folder is processed by Fulfillment. The existing issue is removed before the new version is loaded.
...
The publishing date of the issue in KLOPTEK is set as soon as the first articles are published. This date will not change with the addition of new articles to the same issue. Currently, Brill has no reporting possibility in place that shows the number of articles in an issue. Keeping track of the “growth” of an issue during the year will therefore require manual intervention.
The publishing date of the issue as shown at brill.com is taken from the first article in the table of contents. Due to the choice to list new articles at the top of the toc, the issue publishing date will change with each added article. For the CAP model the issue publishing date does not make sense. Through the @specific-use=”CAP” added to the <fpage>-element, CAP journals can be recognized, and the issue publishing date can be suppressed at brill.com.
The fixed issue publishing date might have consequences for Finance. For subscription-based journals turnover is taken as soon as the issue is published. Dividing turnover according to the “growth” of the issue will require also manual intervention.
The internal archiving procedures are issue based. As part of uploading an issue package to brill.com, the package is also archived in Brill’s digital vault. Since the filename of the issue only contains issn, volume and issue information, each next package will have the same name and – as a result – overwrite the previous version of the package. This is another reason – besides ordering new articles at the top of the table of contents – to include all earlier published articles in the package. Update of the archiving procedure is necessary to be able to load article-by-article. This update could be to include the number of the first article in the name of the zip-file, or – better – no to archive the zip-files, but to unpack these into a folder per issue. Additional articles can be added to the corresponding folder.
The alerting system implemented at brill.com is issue-based. For CAP-journals a different alerting system might be necessary.
Distribution of journal content to third parties, indexing services, etc. is also issue based. Most of the receiving parties do not appreciate to receive the same content multiple times. For CAP-journals an article-based distribution is more appropriate.
To implement an article-based production process at Brill will require:
An update of the platform to be able to set the sort order for CAP journals (Loading of separate articles is no problem, it is mainly a matter of ordering the articles. Based on the @specific-use in the <fpage>-element the sort order of articles could be set to descending on @seq for CAP-issues and ascending on @seq for regular issues).
An update of the archiving procedure to make sure that a new article package does not overwrite the previous version at Q: AWS.
