Adding a New Resource¶
Getting Started¶
Reminder
Your first step each time you open the tool should be to set your working data package directory.
- If you have not yet set your working data package directory this session, do so before attempting to annotate.
-
If you have not set your working package directory before attempting to annotate a resource, the tool cannot automatically generate your resource-ID or connect your resource to your data package folder. You will receive the error message below.
-
Navigate to the "Add Resource" tab and select "Add a new resource."
-
The tool will look through your set working data package directory to determine whether there are existing annotated resource files saved in the folder and will automatically generate the next sequential Resource ID (e.g., result-1, result-2, etc.).
- The User Status Message Box will display a message to acknowledge this:
Filling Out the Form Fields¶
Tip
- For additional information about each form field, please refer to the Resource Tracker schema
-
Hovering over each field in the form will provide additional information about what should be contained in the field. For example, for the Resource Title field:
- Fill out the Resource File Path and Resource Description.
-
Select a Resource Category.
- Based on the Resource Category selected, additional fields will appear within the form.
Resource Categories (and Sub-Categories)¶
Below is a table of all the resource category and sub-category options for your reference. The table also contains information on which fields will appear when you choose a specific category or sub-category.
Resource Category | Sub-category | Additional Resource Annotation Fields for Category |
---|---|---|
Publication | Peer-review manuscript Report White paper Presentation Poster |
|
Result | Multi-panel figure Single-panel figure Table Text |
|
Tabular-data | Raw data Processed intermediate data Processed final data |
|
Non-tabular-data | Raw data Processed intermediate data Processed final data |
|
Metadata | HEAL-formatted data dictionary Other formatted data dictionary Protocol Analysis plan HEAL-formatted results tracker Other |
|
Code | No sub-categories |
|
Experiment Resource 'Belongs' To¶
- This option allows you to associate your resources directly with experimental research questions and hypotheses, which can be useful for future researchers trying to understand your experiments and findings.
-
This field pipes in all existing experiment names from the Experiment Tracker into a drop-down menu.
- To use this option, you will need to enter experiment names when you are documenting your experiments in the Experiment Tracker. If you do not yet have experiments documented with names, you can still annotate your resource. You can just come back and use the edit feature to edit your resource annotation to associate that resource with an experiment later.
Associated Files/Dependencies¶
This is where you will list dependencies associated with the resource. How you record dependencies will depend on your annotation approach. For more information about how to decide on your annotation approach, refer to the HEAL data packaging guidance documentation.
Regardless of your annotation approach, there are two ways to add "Associated Files/Dependencies" in the form.
Warning
You should only utilize one of the below methods for entering dependencies for a specific resource. If you add some files as associated files/dependencies manually and then utilize the "Add Multiple Resource Dependencies" option, those files may overwrite the files you entered manually.
-
Manually adding Associated Files/Dependencies
- If you are adding only a few associated files/dependencies, you can add each individually using the "Associated Files/Dependencies" arrow button:
-
Batch adding Associated Files/Dependencies
- If you would like to add many associated files at once, you can use the "Add Multiple Resource Dependencies" option, which can be found at the top of the window:
- Fill in this field with associated files/dependencies using drag and drop.
- The files you add via drag and drop will automatically appear in the "Associated Files/Dependencies" section of the form.
Access¶
This specifies the level of access that you will apply to this resource (permanent private, temporary private, restricted access, or public).
-
If you select "temporary-private," you will need to complete two additional fields to specify: 1) the level of access for the resource after the temporary private period and 2) the timepoint of the end of the temporary private period (Access Date).
- First, add an additional row and select the designated level of access of the resource once the temporary private period ends.
- Fill in the "Access Date" when the temporary private period will end. This can just be a projection; you are not bound by this date.
-
For other access levels, you will not need to complete these additional steps.
Software used to produce/read the resource file¶
If specific or proprietary software is required to open or read the resource, you should fill this out.
This field is not required. If no special/proprietary software was used to produce/read the resource file, leave this field blank.
Resource Note¶
This field should be used for any additional notes that are not already covered in the other fields of the Resource Tracker but that would be important for someone viewing or re-using a resource.
Adding Multiple "Like" Files¶
If you have multiple "like" files with a similar naming convention, you may want to add and annotate them all at once rather than individually. The tool has a special feature that you can utilize to annotate multiple "like" files all at once.
What are "like" files?¶
- Examples of "like" files may be multiple datasets where each is a run of the same set of experiments or experimental results where each dataset corresponds to one subject's data. "Like" files will also have the same file extension.
-
To use this feature in the tool, "like" files should follow a common naming convention:
-
For example, multiple data files by subject ID grouped in folders by week would be "like" files. The naming convention here is week-#/subject-#
-
Another example: for an experiment testing samples on multiple different dates, files could follow the naming convention sample_1_date_20230818, sample_2_date_20230818, etc.
- If you have "like" files, but they don't follow a common naming convention, you may want to re-name the files (applying a common naming convention) before using this feature.
-
If you have determined that you have a set of 'like' resources that you would like to annotate all at once, follow the steps below.
How to add multiple "like" files¶
-
Select "Add Multiple 'like' Resources"
-
Drag and drop all "like" files you want to annotate together. The first of those files paths will appear in the "Resource File Path" field in the form.
- If your "like" files are in "like" folders (as in the above example of week-#/subject-# structure), you can drag the folders into the box, and the tool will unpack them for you.
-
Once you add your "like" files, a box will pop up asking you to add a naming convention. Enter a naming convention for your like files in the "Resource File Name Convention" box shown below:
-
Follow the instructions in the dialog box above as to how to create a naming convention. Specifically, make sure that you use the {} brackets to bound the number, date, or descriptive information that changes from one like file to another.
- You will specify your naming convention slightly differently depending on whether the common naming convention it is integrated within the directory structure (e.g., multiple data files by subject ID grouped in folders by week) or within the filename (e.g., multiple data files within the same directory that only differ by filename).
-
If your naming convention is within the directory structure:
-
Copy the file path from the Resource File Path field and paste into the Resource File Name Convention box:
-
Change the piece that changes from one like file to another to a descriptive name within {}. Do not remove the file extension from the path (e.g., .txt, .csv, .xlsx).
-
Select "Apply Name Convention."
-
Check the User Status Message Box to confirm that your naming convention was able to be applied.
-
If you receive an error in the User Status Message Box, review your naming convention and ensure that:
- You have used {} to bound the changing number, date, or information that varies among your like files.
- You have retained the file extension in the path.
- Your files are actually "like" named.
-
If the User Status Message Box prints a successful result, also refer to the "Resource File Description" to confirm that the naming convention was applied how you intended:
-
-
If your naming convention is fully contained within the file name:
-
You should only include the file name in the "Resource File Name Convention" field (rather than the file path).
-
Select "Apply Name Convention."
- Check the User Status Message Box to confirm that your naming convention was able to be applied.
- If you receive an error in the User Status Message Box, review your naming convention and ensure that:
- You have used {} to bound the changing number, date, or information that varies among your like files.
- Your files are actually "like" named.
-
If the User Status Message Box prints a successful result, also refer to the "Resource File Description" to confirm that the naming convention was applied how you intended.
-
-
Saving Your Resource¶
Once you have finished entering the resource information, select "Save resource."
Warning
Make sure you do not have your Resource Tracker open before trying to save.
If you attempt to save a resource but have the Resource Tracker open, the annotated resource file will not save. You will receive this error:
To save your resource, you will need to close the Resource Tracker and then press "save resource" again.
-
After you select "Save resource," the User Status Message Box should display a message confirming that your resource file saved successfully and that the resource has been written to the Resource Tracker file:
- This message will also include a note about all the files you listed as associated files/dependencies for your resource. Each of these dependencies will also need to be documented as a resource.
- To make this process easier, these files will automatically be pulled into a resource list, which you can access via the "Check Resources to Add" tab.
- You will be able to use the "Check Resources to Add" tab to directly select and document specific resources from the list.
- This message will also include a note about all the files you listed as associated files/dependencies for your resource. Each of these dependencies will also need to be documented as a resource.
-
Although the tool will automatically add your resource to the Resource Tracker as part of the "save" process, your individual resource annotation file will also be saved as a .txt file within the dsc-pkg folder.
Note
Once you have created them, you will not generally need to interact with the annotation files (.txt files) directly unless:
- You need to edit an existing annotated resource
- There was an error in automatically adding the resource to the Resource Tracker, which would necessitate manually batch adding resources to the tracker
Next Steps¶
- After you have saved your resource, you can annotate a new resource.
-
If you would like to annotate a new resource, you can select "Clear form" at the top of the Annotate Resource window. This will reset your form and generate the next sequential resource ID, so you can start annotating a new resource.
- The User Status Message Box will print a message confirming your form was successfully cleared and that the new sequential ID has been generated.
-
Tip
If you need to annotate a new resource that is very similar to a previously annotated resource with only some slight changes, you can also use the advanced option "Add a new resource based on an existing resource."
This will allow you to copy the information from a previously annotated resource into a new resource, for ease of annotation.