Documentation: status graph for printing process #11
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here's my take on the flow of things when it comes to printing in Alma, and post-processing the printout using APE as described in Issue 5. I tried to include all the configuration points needed for the printing process itself.
What is already included in the documentation are a few extensions which I'll offer one pull-request at a time:
Since some callnumber schemes lend themselves less graciously for use in APE (see Issue 6), I switched to using the barcode and added print_barcode as identifier for that. Similar with print_patron: some printouts (mostly reports including several items) cannot use the identifier for a specific item, and therefore I'm including the Patron ID in its place as part of the filename.
And then there's print_suppress which is used as a hook to not print a particular printout.