URGE Updates
Updates and changes in this release.
Total page views (main page): 1493
Readme button triggers
URGE V1.4
- DOI QR: Added a QR icon button next to the DOI field to generate a 1024×1024 PNG QR code that links directly to the dataset DOI (doi.org).
- Contact QR: Added a QR icon button next to the Email field to generate a 1024×1024 PNG vCard contact QR code (Name, Institution, Email) that can be saved as a contact when scanned.
- In-memory PNG output: QR codes are rendered as PNG in memory and returned as a blob response (no files are stored on the server).
URGE V1.3
- A function was added to track the trigger counts of buttons created in the Readme.
- The data source is now configurable so that data can be fetched from sources other than DataverseNo. DataverseNo remains the default; if users want to work with a different Dataverse, they can remove the default dataverse.no option in the Dataverse Metadata Import section and add their own Dataverse URL.
- Security infrastructure was updated and additional safeguards were added.
- After the user finishes (downloads README or JSON file), the API cache (session metadata) on the server is cleared automatically to free memory and avoid retaining sensitive data.
- A new security notice was added under the Dataverse Connection accordion, reminding users that their Dataverse API key is never stored on the URGE server and recommending that they revoke the key in Dataverse after generating the README, unless it is actively used in other systems.
- ORCID search: In the Contact Information section, the “Search ORCID” button now looks up ORCID records by name (given name and family name) without opening the ORCID website. After you enter a name in the Name field and click “Search ORCID”, matching results appear in a dropdown below the ORCID field. Each line shows “ORCID ID – Family name, Given name” (and institution when available). Selecting an entry fills the ORCID field with that identifier.
URGE V1.2
- JSON option added to the Readme import section; reports imported via URGE with JSON can now be fully retrieved.
- Option to import information from txt files added to the Readme import section. The number of parameters that can be read from txt file data has been increased.
- Grammar check information and consent form added.
URGE V1.1
- Dataverse metadata import errors fixed.
- API access for ORCID record enabled.
- The following fields can now be added without using the API:
- Contributors
- Data Type
- Date of data collection/generation
- Geographic location
- Funding sources
- File Information file checking rules revised.
- Sharing section: optional fields can be added as plain text or fetched from Dataverse via API.
- Warning added for Anonymous Readme (disclaimer that full anonymity is not guaranteed).
- Template updated to USN standard colours.
- Readme.txt revised.
Back to URGE