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
situation - someone creates an experiemnt with biosource K562 and someone else wants it to be K-562 ...
users keep creating essentially same objects with different names - how do we consolidate that ?
another related issue - when cloning an experiment we reference original biosource objects , e.g. K562, so whenever one modifies them - they are modified throughout the database - should we create copies ? - which often would be identical ...
routine database deduplication ?!
The text was updated successfully, but these errors were encountered:
Temporarily:
To avoid modification throughout the database, we have removed the access to edit/delete Individual and Biosource once the experiments are created.
Edit/Delete for Biosample is available with a warning message indicating what will happen if changes are made.
(This allows for experiments to be cloned easily since most of the users clone experiments and major changes are at Biosample and experiment level)
After the above code changes, shared objects can only be modified from the admin side.
situation - someone creates an experiemnt with biosource K562 and someone else wants it to be K-562 ...
users keep creating essentially same objects with different names - how do we consolidate that ?
another related issue - when cloning an experiment we reference original biosource objects , e.g. K562, so whenever one modifies them - they are modified throughout the database - should we create copies ? - which often would be identical ...
routine database deduplication ?!
The text was updated successfully, but these errors were encountered: