Data structure: Difference between revisions
No edit summary Tag: 2017 source edit |
No edit summary Tag: 2017 source edit |
||
| Line 4: | Line 4: | ||
Data structure: | Data structure: | ||
* Add person | * [[Add person]] | ||
* Add | * [[Add organization]] | ||
* Add experience (link to person) | * [[Add experience]] (link to person) | ||
* Add project | * [[Add project]] | ||
* Add article (link to persons, projects) | * [[Add article]] (link to persons, projects) | ||
Revision as of 18:10, 7 March 2025
7 Marzo 2025
Data structure:
- Add person
- Add organization
- Add experience (link to person)
- Add project
- Add article (link to persons, projects)
Should the experience form contain a link to the related project or to a referent staff member ?
2 Dicembre 2024
Here we can discuss the overall data structure of the website.
For instance for now we have created a schema "Volunteer / Organization participant" which contains partially the data of a class "Person" (see here https://schema.org/Person) plus some additional data, like organization affiliation, etc. -- But actually we could "recursively" subdivide the form, into another child form, and create a more generic schema for a person. Then this class person can be used as a component for the form "Volunteer / Organization participant".
This would allow much more flexibility in using the data related to a person in different cases.