Job tagging/notation

Basic question here. I have a user that runs many Jupyter Lab jobs concurrently but it’s becoming difficult to keep track of his tasks/purpose for each app launch. Is there a way to tag/notate the running jobs? My solution for him at the moment would be to copy the Jupyter app into his /dev and change the manifest based on usage but that seems clumsy. Perhaps there’s a form entry that would be useful that I’m missing.

John

If the user is a developer then they can change the job name, perhaps dynamically.

The user could drop an info.md.erb file in the root of the dev project and add notes to the card.

Here’s how we use this feature to add instructions to our Rstudio app about how to load modules into the app.