Skip to content

Conversation

@NielsGeudens
Copy link
Contributor

Updated documentation on download/upload feature and its sample linkage
Updated documentation on SOPs

Closes #67
Closes #2334
Closes #2311

…e" for sample linking.

* Better defined how to find sample id to use for linking samples in dynamic table
Adding link to "create samples in an study" section in user guide
@NielsGeudens NielsGeudens added the documentation Improvements or additions to documentation label Nov 3, 2025
Copy link
Contributor

@floradanna floradanna left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added few suggestions: I would keep the SOP page simple and general. ISA-JSON specific info related to SOP should not be included in the general SOP page, but in ISA-JSON specific pages, where necessary

@NielsGeudens
Copy link
Contributor Author

Hi Flora,
Thank you for the suggestions. I have made changes to keep the SOP documentation more general, free from ISA-JSON specifics. The references to protocol_type are commented out for now.

Copy link
Collaborator

@PhilReedData PhilReedData left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've left some formatting and style comments, and one about navigation.


Standard Operating Procedures (SOPs), also known as Protocols, describe the steps required to reproduce an assay or part of an experimental workflow.

SOPs can be uploaded in various formats (Word documents, PDFs, e-lab notebooks, code scripts, annotated spreadsheets, etc.) and stored as assets in SEEK. These assets can be linked to Assays (and in ISA-JSON compliant setups also to Studies) to document the procedures applied.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
SOPs can be uploaded in various formats (Word documents, PDFs, e-lab notebooks, code scripts, annotated spreadsheets, etc.) and stored as assets in SEEK. These assets can be linked to Assays (and in ISA-JSON compliant setups also to Studies) to document the procedures applied.
SOPs can be uploaded in various formats (such as Word documents, PDFs, e-lab notebooks, code scripts, annotated spreadsheets) and stored as assets in {{ site.seek_instance.name | default: "FAIRDOM-SEEK" }}. These assets can be linked to Assays (and in ISA-JSON compliant setups also to Studies) to document the procedures applied.

Avoiding Latin abbreviations. Adding the instance name field.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Delete Paste From Clipboard from DT Update SOP documentation Adjust documentation about upload / download feature

4 participants