Proposal to use public facing platform to host content for 2021-09-30…

[hanisahkz]

…-data-maturity-open-source.md

Context Some of the content points to a location that is not open to public or face the risk of being re-located (hence, dead link).

Proposal To use public facing platform to host content (e.g.: .pdf) for MERL content. The platform can be (not limited to) GDrive, Github repo (same repo or different repo) as this promotes better control over the content availability (less prone to dead link), anyone can help ensure latest content is used.

Approaches for consideration

• GDrive
  • Requires an owner of the drive to make a folder public
  • However, as content increases, more storage will be needed, hence incur higher storage cost
  • GitHub
  • Content is maintained by the public
  • Better tracking for content update (via commit history)
  • Recommend repository size is less than 1GB with a somewhat hard limit of 5GB. Ref.

Demo For demo purposes, I'm using a non-public GDrive to host the content being referred to. Roughly, regardless of the platform, should this proposal be accepted, the process will be similar:

1. Upload content to the platform
2. Use the generated link in the MERL content

Thank you in advance for your input!

[ronna]

+1 for the proposal. I recommend we host the content on GitHub.

[scoker-me]

I think this is a good idea as well. Adding to MERL Center admin agenda for consideration. I'll update next week.

[scoker-me]

decided to go ahead and adopt the policy suggested

Next steps:

• Create mechanism for finding broken links (Bonnie) https://github.com/MERLTech/merl-center/issues/97 and an issue to follow for automated checking
• Create local copies moving forward (Everyone) link for PDFs: https://github.com/MERLTech/MERL-Center-public/tree/main/assets/img
• Change editorial guidelines and update editor checklist in content template (Stephanie)
• Socialize at next month's content check in (Stephanie)