Difference between revisions of "V3 PubProcess - Submit Content"
| Line 18: | Line 18: | ||
===Acknowledge (if HQ)=== | ===Acknowledge (if HQ)=== | ||
The final step, in the case of a submission to HQ, will be the return of an acknowledgment to the submitter. | The final step, in the case of a submission to HQ, will be the return of an acknowledgment to the submitter. | ||
| + | |||
{{to-top}} | {{to-top}} | ||
Revision as of 14:56, 21 July 2010
Contents
Content Submission
This section encompasses those steps undertaken by a Publishing Facilitator (or other person preparing part or all of a publication package) in order to assemble and "submit to publishing" their specific portion of the content. Note that in this context, "submit to publishing" means either to submit to HQ for publishing or to "submit" to oneself for local publishing.
Steps:
ID and Mark Submission Files
The initial step in the publishing process is to identify those files that are to be used for publication. Although it would be desirable to be able to identify a set of files from within the directory structure for use, the SVN system does not permit "tagging" selected files within a directory. The SVN tags actually mark complete directories or complete projects.
For this reason, the primary approach to identifying files will be to analyze the primary content (the domain text, or the primary document from a stand-alone publication) and from that to identify what are the artifacts, image files, etc. that must be collected to publish the document. This process is a bit like following the "links" from an HTML document, but in this case is actually tracking the references from the primary document became sure that the targets of those references exist, and then analyzing the targets for their references, etc.
The first step will be to extract the primary document (in the case of a domain it is extracted from the publication database), and analyze this document for its references. Transforms to accomplish this or are already part of the desktop publishing process.
The manifest from this review will produce either a ZIP file of all content or a file list that may be automatically applied to SVN to extract the desired content. (Current 7/21/10 capability is only the ZIP file.) Once the package is assembled it needs to be "placed" (either Gforge or SVN) where the recipient of the submission can use it.
Notify (if to HQ)
When the submission is packaged, HQ needs to be notified, if this is a submission or a ballot or a Normative Edition.
Version and Download
The recipient will extract the submission and assure that it is properly placed in the SVN system for the publication being prepared.
Acknowledge (if HQ)
The final step, in the case of a submission to HQ, will be the return of an acknowledgment to the submitter.
