An example of using the add_additional_resource function of the Submission or Table objects is not given in either the documentation or any of the example notebooks. This issue came up in a HEPData Forum post. It would be good to document the usage of add_additional_resource and apply it in one or more of the example notebooks.
Also, we just added a new feature to highlight HEPData records with attached HistFactory JSON files (search for analysis:HistFactory). Currently the "HistFactory" type is triggered by looking for certain words ("histfactory", "pyhf", "likelihoods", "workspaces") in the "description" for certain file types. But we now also allow a type: HistFactory field in the submission.yaml file to avoid relying on the description (see submission docs). So it would be good if add_additional_resource could also accept an optional argument type, then set resource["type"] = type.
An example of using the
add_additional_resource
function of theSubmission
orTable
objects is not given in either the documentation or any of the example notebooks. This issue came up in a HEPData Forum post. It would be good to document the usage ofadd_additional_resource
and apply it in one or more of the example notebooks.Also, we just added a new feature to highlight HEPData records with attached HistFactory JSON files (search for
analysis:HistFactory
). Currently the "HistFactory" type is triggered by looking for certain words ("histfactory", "pyhf", "likelihoods", "workspaces") in the "description" for certain file types. But we now also allow atype: HistFactory
field in thesubmission.yaml
file to avoid relying on the description (see submission docs). So it would be good ifadd_additional_resource
could also accept an optional argumenttype
, then setresource["type"] = type
.