How to report software outputs in Pure
This guide has been written with reference to the Pure instance at the University of St Andrews, which is version 5.13.1 at the time of writing.
Create a new Research Output from template Non-textual form->Software
Then you will see the following input form:
Enter details for Publication status and dates. Published and Unpublished are likely to be the relevant options, with Published being appropriate for open-source software.
Enter the publication information. Note that the mandatory Original language field does not refer to programming languages.
Leave Media of output as No value, or specify Online for software publicly available for downloads.
Add Contributors. Here you can search and add an internal contributor by their nbame, or create an external person.
After choosing an internal collaborator, you will see the next window.
The list of roles here is not really suitable for software projects (this is something to ask Pure developers in the future), so for now Author is likely the most useful role. There is no suitable role for maintainers, testers and other contributors who are not authors - for these, you should use Other.
After adding a new author, you will see the extended list of authors:
Change the Managing organisational unit if necessary.
Add Publisher information.
Potentially relevant options such as GitHub and Zenodo may already be available, or they can be created. If the software is available from its webpage, but not published via some repository, you can leave this field blank.
The next section, Electronic version(s), and related files and links, is where you can link to an external resource and/or upload files. In particular, if you have a DOI you should add it here, along with details of the applicable license.
For example, below is what is used for the release of the GAP system, version 4.10.1:
This is a link to the downloads page for the official GAP distribution:
This is a link to the corresponding tag in the GAP repository on GitHub:
If adding any keywords, try and be consistent with what you have used elsewhere (e.g. on GitHub) but try and avoid creating new keywords unnecessarily.
Add details of any Relations the record has to any existing records in Pure
- Research Outputs (papers), Activities, Projects, Datasets etc.
Finally, set the Visibility according to how you wish the record to be available and press Save.
How to import code to PURE via ORCID
This guide has been written with reference to the Pure instance at the University of Birmingham, which is version 5.14.1 at the time of writing.
Prerequisites:
- You will have to have your code listed as a research output on your ORCID record. You can do this manually or, if your code has a DOI assigned through zenodo or figshare, via ORCID’s search and link functionality using the DataCite wizard.
- Your institution has enabled ORCID as an import source for PURE.
Create a new research output by choosing “Import from online source” and pick ORCID
Search using your ORCID identifier and you will get a list of records on your ORCID profile that are not on PURE yet. Pick the one you’d like to add and click import.
This will add most of the metadata automatically and you will just need to ensure that creators are mapped correctly to researchers at your institution.
The import will automatically choose the template Research output-> Other contribution. You will change template to Non-textual form->Software as shown above.
You can now add any other information following the steps lined out above.