Tags
Free-form labels you can attach to any job, workstation, or file, then search with boolean logic. Tags need no setup and no schema, which makes them the quickest way to make a large set of jobs findable.
For structured data that can be required, see custom fields instead.
Add a tag
Anyone who can see a resource can tag it, and tagging is always done from the resource itself rather than from a central admin screen.
- From the Tags column, click the + on the resource's row.
- From the resource detail view, click the same +.
- In bulk, select several resources and use + Add Tag, next to Archive and Download CSV.
Search existing tags in the dropdown, or type a new one. A new tag appears in blue with (new) next to it until saved.
You can also tag a job on the setup page before submitting. Duplicated jobs and jobs from a template inherit the source's tags.
Tags do not travel between a job and its files, though. Tagging a job leaves its input and output files untagged, and using a tagged file as a job input does not tag the job. If you want both findable under one term, tag both.
Remove a tag
Click the × next to the tag.
Tags can be added in bulk but removed only one at a time. There's no bulk-remove and no undo.
Plan around it by agreeing a naming convention before tagging at scale, and by being deliberate with bulk-add. A mistaken bulk-add across 200 jobs has to be unpicked one job at a time.
Search by tag
Clicking is quicker, typing is more precise, and both reach the same results.
The Tag Cloud sits lower-left, under Tags, and shows a count per tag. Click one to filter; click several to combine them with AND. Selected tags show as solid.
The search bar opens a dropdown of every tag when you type #.
Boolean logic lets you combine terms with AND, OR, NOT:
#performance AND NOT #DOE
#failed OR #issue
You can mix tag and name search: #performance Amber finds jobs tagged #performance whose name contains "Amber".
Wildcards
* works in any position:
#Quote it ("#foo") or the search resolves to a tag instead of the name.
Speed up a slow Jobs page
If the Jobs list is slow, tag by team or study, run the tag search, and bookmark the resulting URL. Pre-filtered views load substantially faster than the full list: Rescale measures over 80% improvement.
https://platform.rescale.com/jobs/?owner=1&page=1&perPage=20&query=%23study%3Aairfoil_flow+&status=0
Substitute your own platform host if your account is not on platform.rescale.com. See platform regions.
How tags behave across a workspace
Tags are case-insensitive and normalized
Rescale normalizes on creation, so a tagging convention holds even across users who can't see each other's jobs.
If someone tags a job study:weight_reduction, a colleague later typing Study:Weight_Reduction sees the existing tag offered in the list. They can't create a second one differing only in case, which is what stops the vocabulary fragmenting into dev, Dev and DEV.
Tags are shared workspace-wide
The tag vocabulary is shared across the workspace so people reuse the same terms. Resources still follow normal sharing rules, seeing that a tag exists doesn't grant access to the jobs carrying it.
Colors are automatic
Colors are assigned randomly, but they are stable per tag value, so a given tag looks the same everywhere it appears. You can't choose them.
Current limitations
Tags were built for finding things quickly, and the gaps below all follow from that. None of them matters much while you are organizing your own jobs; they matter a great deal if a process or an audit comes to depend on a tag being correct.
Tags are hard-deleted, so there is no record that one ever existed, and no admin can recover one. If something you need to defend later depends on this metadata, do not let a tag be the only place it lives.
Taken together, no admin cleanup and no bulk remove mean a misspelled tag adopted across a workspace is effectively permanent. That is the strongest argument for agreeing a convention before anyone tags at scale.
Useful patterns
Rescale imposes no formatting rules at all: spaces, capitals and emoji are all accepted. That means the value of a tagging scheme comes entirely from the convention you agree on, and lowercase snake_case is the one to pick, since normalization is case-insensitive anyway and consistency is what makes search work.
The patterns below are the ones Rescale customers use most. The common thread is a key:value shape, which keeps related tags together in the dropdown and lets a wildcard search like #study:* pull back a whole family at once.
Populating tags automatically
A post-processing script can extract values from job output and write them into tags, so fatigue_failure:yes is set by the run rather than by hand. See automations.
API
Tags are available through the REST API for reading and writing, which is how PLM and external system integrations consume them.
Related
- Custom fields — structured metadata that can be required
- Automations — populating metadata from job output
- Find and manage your jobs — the wider search syntax
- Sharing — tags don't override access rules
- Files and storage — tagging files