Is your feature request related to a problem? Please describe.
Currently, to update a bioschema class, we 'extend' from the class to be updated (A). The extended class (B) will inherit properties and validation rules from A, but the parent of B will equal A. This means that the user must manually edit the parent class of B to the parent class of A. Hence, updating a bioschemas class requires editing the JSON-LD file, even in the cases where updates to be made are marginality or descriptions which require NO knowledge or understanding of JSON-LD.
Describe the solution you'd like
Have a 'clone and modify' option which is exactly the same as the 'extend' process. The only difference is on the backend where the cloned/modified schema will have the same parent class as the class it's being clone/modified from. Include in the FAQ what the difference between the two functions would be.
Not sure what's the best name for this function should be:
clone and modify: Pro- does not mislead user into thinking that they won't need to run through the registration process or refresh button. Con- Not immediately obvious why this process would be used in lieu of the extension process
update/modify: Pro- easy to see the difference between this function and extension. Con- the resulting JSON-LD file will still need to be processed via github actions or by other community members. 'Update/modify' suggests that any changes made on the UI will be directly saved to the backend of the UI, which is not going to be the case for any schema maintained by more than one person.
Describe alternatives you've considered
We tried to provide simple instructions for how to update just the parent class part of a JSON-LD file but this activity was deemed too technical for non-technical bioschemas community members
Additional context
Add any other context or screenshots about the feature request here.
Is your feature request related to a problem? Please describe. Currently, to update a bioschema class, we 'extend' from the class to be updated (A). The extended class (B) will inherit properties and validation rules from A, but the parent of B will equal A. This means that the user must manually edit the parent class of B to the parent class of A. Hence, updating a bioschemas class requires editing the JSON-LD file, even in the cases where updates to be made are marginality or descriptions which require NO knowledge or understanding of JSON-LD.
Describe the solution you'd like Have a 'clone and modify' option which is exactly the same as the 'extend' process. The only difference is on the backend where the cloned/modified schema will have the same parent class as the class it's being clone/modified from. Include in the FAQ what the difference between the two functions would be.
Not sure what's the best name for this function should be:
clone and modify: Pro- does not mislead user into thinking that they won't need to run through the registration process or refresh button. Con- Not immediately obvious why this process would be used in lieu of the extension processupdate/modify: Pro- easy to see the difference between this function and extension. Con- the resulting JSON-LD file will still need to be processed via github actions or by other community members. 'Update/modify' suggests that any changes made on the UI will be directly saved to the backend of the UI, which is not going to be the case for any schema maintained by more than one person.Describe alternatives you've considered We tried to provide simple instructions for how to update just the parent class part of a JSON-LD file but this activity was deemed too technical for non-technical bioschemas community members
Additional context Add any other context or screenshots about the feature request here.