|Jesse Griffin 4ec6a77e98||1 year ago|
|.github||1 year ago|
|forms||2 years ago|
|README.md||3 years ago|
|instructions.md||2 years ago|
Please feel free to use the instructions. To use the instructions:
Position the instructions in one window alongside another window that has the form.
If you are looking for more information about publishing, please see the Publishing Section of the tA Process Manual.
The Approver will review the requests and do one of the following:
The Help Desk may help with this process if needed by the Approver.
Once the Content Tech receives the ticket, he or she will review the formatting of the data to make sure there are no errors and will fix them if needed. The project will be forked or copied into the STR organization so that the whole publishing team can make formatting and metadata updates as needed.
If the Content Tech cannot make the necessary changes then he or she will label the request as "Content Format Issue" and let the requester know what needs to be changed before publishing can continue.
Once the project is ready, the Content Tech will comment on the initial request to let the Publisher know that the content is ready for publishing. He or she will also label the request as "Ready" and assign it to the Publisher.
Once the Publisher has been assigned the ticket, he or she will double check the manifest information and the content formatting. Then the following steps will take place:
At this point the Publisher will comment on the request to let the requester know that the content should be available in the catalog soon. The publisher will apply the "Published" label and close the request.