create standards and protocols for adding and editing resources

[njr2128]

Based on M&K's sandbox protocols, but THC and NJR need to adapt.

Some notes from NJR&THC:

From NJR & THC & CMS: Video considerations:

• Formats, standards, and protocols

  • https://github.com/cu-mkp/sandbox/blob/main/publishing-to-sandbox.md

• For syllabi:

  • keep original and clean up as needed
  • creating html versions?
  • Or create a template? [likely not]
  • Maybe submit to https://www.opensyllabus.org/?

• Collaborator videos

  • Hosting and streaming (we are using a commercial service - Vimeo - what happens if they go away?)
  • Proliferate across services: Flickr, Youtube, Vimeo, look into AWS self-streaming options(?)
  • Think about cost and maintenance of this
  • Archiving
    - Eg through Academic Commons (what we have done for the lab tour playlist) - but need CU Libraries
    - https://academiccommons.columbia.edu/doi/10.7916/d8-8r5c-2564
  • Zenodo? Does not have a player but can archive
  • Formats
  • Captioning - time-consuming!
  • Other ADA compliance and accessibility concerns?
  • Are there any permissions or consent/contributions considerations?

[njr2128]

To do, in https://github.com/cu-mkp/research-teaching-companion/blob/main/how-tos/publishing-to-sandbox.md:

• describe relationship bw content/ and static/ (esp static/documents which can be thought of as "downloads")
• decide on acceptable file formats
• confirm naming protocol (pull from sandbox protocols and from fieldnotes protocols)
• externally-stored assets - eg are there any items we want to make available/maintain in external cloud storage eg S3 (for large-size or high volume materials) -- PHS says we maybe should do an S3 bucket for images
• protocols for linked items - what kinds of resources do we expect to meet our sustainability plan? Make sure to use persistent IDs (eg doi), is there an archived version stored in an external repository? Do we want to make sure the pages are available through internetarchive (what are the steps for this)?

workflows to do:

• methods for addressing git conflicts (which is mostly addressed from the get-go by using our workflow: https://github.com/cu-mkp/research-teaching-companion/blob/main/how-tos/github-local-setup-and-workflow.md)

[njr2128]

The outstanding issues are now covered in #50 and #42