User Flow
Role: Review Committee member
Note: URLs listed below are not implemented
After a reviewer reads and approves a Google document, the reviewer
- moves the document to a Google directory with add/update privileges for reviewers only to protect it from being updated
- enters metadata about the document into the Knowledge Base system.
- If a record already exists for the Google ID of the doc, the reviewer updates the status of the record to Prod.
- If no record exists, the reviewer creates a new record and specifies the metadata, including Google ID, slug (end part of URL), and status (Prod)
- sets Publish flag to true
- automatic process converts to markdown and pushes document to gh-pages branch
- Author copies document to Google directory
- Author revises
- Author moves to directory for review
- Reviewer reviews and approves
- Reviewer moves the document to a Google drive that is protected for reviewers only
- Reviewer finds record in knowledgebase for the published version of the document and updates the Google ID to the version to be published
- Open document. Copy the id from the URL. The id is the string after "document/d/" and before the next /. For instance, if the URL is https://docs.google.com/document/d/1xbSEeJ/edit#heading=h.bhu3xwabsivh then the id will be 1xbSEeJ.
- Log in to system (https://hackforla.org/knowledgebase)
- Select Add next to GDocs.
- Paste the id into the Google ID field.
- Fill in the rest of the data. If you don't see a value in the list you can add values.
- Automatically populate Knowledgebase with metadata when a Google document is created
- Create Google Docs plugin to open up Knowledgebase for an opened Google Document
- Add non-automatic filters to Django Admin UI for Knowledgebase