Update frontmatter for new and old profiles

[catherinet1]

This issue is to implement the latest agreement re what metadata fields we're adding to profiles for the time being: #143

Acceptance

• [ ] Cohere template is up to date, including guidance on field definitions
• [ ] All new orgs in tbd folder are up to date with the latest template
• [ ] All 2021 orgs in profile folder are updated
• [ ] Code is updated to build with new metadata

Tasks

• [x] Update the cohere template including docs for field definitions https://docs.google.com/spreadsheets/d/1YcIQP_CGYhpMTzEQU_f46j159UalqLVfGt2chhsoQxw/edit#gid=1239522110 Template is up to date, but currently includes template and documentation/guidance in the same file. Next is to create clean version of template with separate documentation
  • [x] Create supporting documentation Cut guidance out of template and pasted it in new file: https://github.com/life-itself/ecosystem/blob/main/content/templates/profile-documentation.md
  • [x] Create clean version of template Updated template file to contain only headings here: https://github.com/life-itself/ecosystem/blob/main/content/templates/profile.md
  • [ ] remove About heading? Haven't done this as helps to have an 'About' section to refer to in the documentation
• [ ] Update existing new orgs (in tbd folder)
• [ ] Update 2021 orgs in profile folder
  • [ ] Update code for that ... (as our current profiles page depends on current metadata structure)
• [ ] Merge tbd into profiles (or even merge everything into the root directory?)
• [ ] Add agreements from notes below into template documentation: https://github.com/life-itself/ecosystem/blob/main/content/templates/profile-documentation.md

Notes

Catherine qs re data collection and input as of 2023-11-30

• [ ] What is our agreement re standard format for filenames? Capital letters? Spaces?
• [ ] When do we start putting things in profile folder? (instead of tbd)
• [x] (Rufus) do we want a clean template and separate documentation guide for filling it in (e.g. template/documentation) ✅2023-11-30 yes i'd just have a file like Profiles Documentation or whatever you like for now - or even just put in the contributors documentation
  • [ ] Maybe put link to documentation in the template (so that people don't just fill in the template without referring to the documentation )
• [ ] todo still: agree on not-found convention
  • [ ] propose: use not-found and not-applicable. e.g. If i don't fill in a location for an org because it is an international network then I want to use something which indicates that this category doesn't apply to this entry. (leaving it empty is ambiguous, and recording it as not-found suggests that I'm missing information as to why it is not-found)
  • [ ] clarify that frontmatter fields should only contain data in the precise format specified in documentation?, e.g. for locations that is [city], country. Otherwise it is too tempting to put in data in other formats when things don't quite fit ..

Agreements

• Put images directly in assets folder
• use obsidian links as easiest, least error prone approach ie. start typing ...[[...]]

[rufuspollock]

@catherinet1 added your additional questions here.

[catherinet1]

cc @matthewmccarthy11 the template is now up to date and the documentation/guidance on how to fill it in is in a separate file

[rufuspollock]

@catherinet1 is this still relevant? If so can we update with current status and next steps. If not, let's close with message about why etc.