You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current forms were build around the schema for each section (OSC, OSS and Open Standards). This worked well for OSC, but is more complicated for other sections.
The OSC schema is based on "one file per administration". This is reflected in the form and selecting the administration is the first part of the form allowing users to then manage the OSS for their administration.
This pattern should be applied for other sections without changing the current schemas.
For example for OSS, users should first select/create the administration, then select/create the software and manage uses of that software for their administration.
Same for Open Standards.
The text was updated successfully, but these errors were encountered:
simon332114
added a commit
to VilledeMontreal/ore-ero
that referenced
this issue
Jan 22, 2020
The current forms were build around the schema for each section (OSC, OSS and Open Standards). This worked well for OSC, but is more complicated for other sections.
The OSC schema is based on "one file per administration". This is reflected in the form and selecting the administration is the first part of the form allowing users to then manage the OSS for their administration.
This pattern should be applied for other sections without changing the current schemas.
For example for OSS, users should first select/create the administration, then select/create the software and manage uses of that software for their administration.
Same for Open Standards.
The text was updated successfully, but these errors were encountered: