NOTE: If you want to create an entirely new book (not move one from legacy) use the /template-osbooks-new repo
Use this repository template to create an "osbooks" repository for migration of content from CNX Archive to Github.
Full list of osbooks repositories via Github Search.
Note: "osbook(s)" repository" and "content repository" can be used interchangably
- Create osbook repository - by using this template repository.
- Seed osbook repository - by updating files the content synchronization pipeline looks for to sync content from archive to github.
- Finalize osbook repository - by creating a github issue to enable syncing of content from archive to github, one osbook per github issue.
-
On GitHub, navigate to the main page of this repository.
-
Above the file list, click Use this template.
-
In the Owner drop-down menu, select openstax.
-
Name the Repository:
- osbooks-book-name, if repo contains only one collection, or
- osbooks-book-name-bundle, if repo contains more than one collection
Note: Repository names can be changed at a later time. Description can be left blank.
-
Set repository visibility to Private.
-
Leave Include all branches unchecked, this template repository only has one branch.
-
Click Create repository from template.
Once the content repo is created:
-
Fill out the
META-INF/books.xml
:- Should contain atleast one
<book />
tag - Where
<book />
contains:- slug: determined by CM
- collection-id:
col#####
- href:
"../collections/<slug>.collection.xml"
books.xml
example<container xmlns="https://openstax.org/namespaces/book-container" version="1"> <book slug="college-algebra" collection-id="col11759" href="../collections/college-algebra.collection.xml" /> <book slug="precalculus" collection-id="col11667" href="../collections/precalculus.collection.xml" /> <book slug="precalculus-coreq" collection-id="col32026" href="../collections/precalculus-coreq.collection.xml" /> </container>
- Should contain atleast one
-
Copy/Paste one of the following into
LICENSE
file: -
Change permissions with manage permissions
- On GitHub, navigate to the main page of this repository.
- On top navigation tabs, click Settings.
- On left navigation, click Manage access.
- Using the Manage Acccess panel, to add:
- openstax/ce-all, Role: Write
- openstax/content-managers, Role: Admin
- openstax/ce-admins, Role: Admin
- openstax/katalyst, Role: Read
- {vendor account}, Role: Write (Note: find the book's vendor under column C here).
- Wisewire:
ww-openstax
- MPS:
mps-openstax
- Six Red Marbles (SRM):
srm-openstax
- Wisewire:
-
Navigate to Create Issue for Repo Sync
-
Title issue "Sync Content Repo
<osbook-repo-name>
" -
Copy and Paste task.md into the body of issue:
task.md
## Description ### Set up for Syncing for following Content Repo: Name of Content Repo: <!-- Name of Content Repo --> Link of Content Repo: <!-- Link to Content Repo --> ## Acceptance Criteria - [ ] [Sync pipeline set up](https://github.com/openstax/content-synchronizer#quick-start) - [ ] Initial content sync is successful - [ ] "CE: Github Repo Stable Sync" column on [Github/POET transition plan spreadsheet](https://docs.google.com/spreadsheets/d/1qbkcpdpION-uN8GWW3zpanpunq4pjwqmVDGPOBhNW-8/edit#gid=0) is updated with hyperlink: - _text_: Date of first successful pipeline job - _link_: Link to pipeline
-
Update the following, in the issue body:
<!-- Name of Content Repo -->
<!-- Link to Content Repo -->
-
Click, Submit New Issue
Once a new issue is submitted this kicks off the workflow to sync the content and eventually get it ready for POET.
- Github/ POET Transition Plan (google spreadsheet)
- Content Synchronizer (github repo)
- Content Repo Migration/ Creation Process (confluence documentation)
- Full List of Osbooks Repos (github search)
- Template Repo for New Book (this github repo)
- Creating a Repository from Template (github documentation)