|
1 | 1 | # HAAG Project Explorer |
2 | | -Metadata for HAAG research projects to display on the HAAG website. |
| 2 | +The goal of this project explorer is to provide visibility into the projects under HAAG. This repository holds the metadata for HAAG research projects that will be displayed on the HAAG website. |
3 | 3 |
|
4 | 4 | ## Template |
| 5 | +This is the template to be used to structure the metadata. For fields (such as links) that you want to leave blank, please populate with `null`. |
| 6 | + |
5 | 7 | ```yaml |
6 | 8 | id: project-id |
7 | 9 | name: Project Title |
8 | | -status: active # Research status. active | completed | pending | archived |
| 10 | +status: active # Research status. active | completed | preprint | archived |
9 | 11 | visibility: private # For code visibility. public (for open-source projects) | private (if not to be publicly visible at this time) |
10 | 12 | faculty: # PI / Faculty |
11 | 13 | - |
12 | 14 | researchers: # List research contributors here |
13 | 15 | - |
14 | 16 | - |
15 | | -advisors: # List computational advisors if any exist on the project |
| 17 | +advisors: # List computational advisors if any exist on the project (if none exist, mark as null). |
16 | 18 | - |
17 | 19 | - |
18 | 20 | summary: > # Summarize the project |
19 | 21 | Summary here. |
20 | | -tags: # Optional for now, but will be used to categorize the projects into groupings (such as unit groups) |
| 22 | +tags: # Optional for now, but will be used to categorize the projects into groupings (such as unit groups). If unknown, mark with null. |
21 | 23 | - |
22 | 24 | - |
23 | 25 | links: |
24 | | - github: https://github.com/... # placeholder, if public |
25 | | - docs: https://example.com/docs # Could be README, wiki, github pages, project website, etc. |
| 26 | + github: https://github.com/... # placeholder, if public |
| 27 | + docs: https://example.com/docs # Could be README, wiki, github pages, project website, etc. |
26 | 28 | publication: https://doi.org/... # If exists/preprint/completed |
27 | | - forum: https://example.com/forum # link to forum - @James Hennessy - await guidance on this |
28 | | - contact: mailto:lab@example.edu # Contact to reach out to for interested parties (lab-level email distribution), or leave blank at this time if there isn't an email distribution that is setup at this time |
| 29 | + forum: https://example.com/forum # link to forum - @James Hennessy - leave null for now |
| 30 | + contact: mailto:lab@example.edu # Contact to reach out to for interested parties (lab-level email distribution), or leave null at this time if there isn't an email distribution that is setup at this time |
29 | 31 | ``` |
30 | 32 |
|
31 | 33 | ## Example |
|
0 commit comments