Describe what Collections are for

[stuzart]

On the new collection page, add some brief text describing what Collections are, and link to the help page in the documentation

[abecam]

Got something working and generic (would allow solving #599). Feedback welcome:

[OlgaKrebs]

I suggest to replace "things" by "assets" . Also " that don't belong to any other kind of hierarchy" sounds like "put the rests toghether" and is misleading, cause one can add to collection assets linked to ISA. Can it be expressed in a positive way? like " to group assets which belongs together in users' eyes" -

[OlgaKrebs]

in a documentation we could write examples like e.g. "collection of project's SOPs ", "collection of project's templates"

[abecam]

The problem with asset is that assets are some specific elements in Seek, while collections accept others as well. A positive way would be great indeed. Any suggestion would be welcome. Maybe discuss it with the other CWs?

I suggest to replace "things" by "assets" . Also " that don't belong to any other kind of hierarchy" sounds like "put the rests toghether" and is misleading, cause one can add to collection assets linked to ISA. Can it be expressed in a positive way? like " to group assets which belongs together in users' eyes" -

[floradanna]

What is a Collection? (info icon) A collection is a group of SEEK items that are conceptually related to each other.

Collections (in the user guide page) A collection is a group of SEEK items that are conceptually related to each other. Items within a collection can be ordered.

SEEK items that can be part of a collection are:

• Assets (except other collections)
• Activities
• Samples

SEEK items that cannot be part of a collection are:

• Yellow pages
• Experiments
• Other collections

[OlgaKrebs]

sounds very good

[abecam]

Both updated.