URGE Updates
Updates and changes in this release.
Total page views (main page): 7909
Readme button triggers
URGE V1.7
- README template: A template choice sits above Data Import. Standard v3.0 is the default and follows the DataverseNO README File Template v3.0 (2026-10-19). DataverseNO v2.4 (legacy) keeps the previous dataset README. Software Code follows the DataverseNO README File Template for software and code (v2.2).
- Sending a v3 README: The file is added as a new
00_README.txt (or 00_README-1.txt, 00_README-2.txt, and so on if that name is already taken). URGE does not change or delete files already in the dataset. Delete the old README yourself in Dataverse or Figshare before you publish. 00_Readme.txt and 00_README.txt collide when a zip is extracted on Windows or macOS. If the new text is identical to a README already in the dataset, URGE does not add another copy. Check Files warns when more than one README is present, or when names differ only by letter case.
- Standard v3.0 fields: The form adds Authors, dates of collection or generation, hardware or software needed to open the files, relationship between files, and Terms of use. The sidebar and the top link say Terms of use. Contributors, Data Type, the old collection-date checkbox, Geographic location, and Funding sources are hidden. The README follows the v3 section order, including the fixed lines after the description for related publications and the recommended citation.
- Updated version: “Is this an updated version of a dataset published on DataverseNO?” is a short choice. NO shows a checked-file icon and is selected by default. The extra fields stay hidden, and the README prints NO with empty lines for the version, date, file name, and what changed, so a later update can fill them. YES shows an updated-file icon and opens Dataset version, Date updated, and Add updated file. Each file asks for its name and what was changed and why. The version is the number the dataset will receive when it is republished, for example V1 becoming V2. This is for changes to the data files, not for small edits to metadata or the README.
- Information buttons: On a long text field, the information button sits above the expand button. On a field without an expand button, it sits to the right of the field.
- Text in hidden fields: Text left in the old additional-methodology or Sharing fields is not included in a Standard v3.0 README. URGE shows a warning. Move copies that text into the v3 fields and clears the old fields. Undo puts the previous text back.
- Anonymous README and imports: An anonymous Standard v3.0 README leaves out contact information and authors. A README text file that uses the v3 sections opens as Standard v3.0. A file from the previous template, or JSON with no schema, opens as DataverseNO v2.4. A Dataverse import fills the v3 contact from the first dataset contact, keeps authors in repository order, formats collection dates, and writes the licence as name, version, and URL.
- Software Code layout: Sharing moves up, Methodology is replaced by How to use the dataset, and Data-specific information becomes Code documentation. A code repository URL is added under Contact. The DOI stays in the form for repository import and upload, and is left out of the Software Code README text.
- Switching templates: Text you already entered is kept when you change template. The README, preview, anonymous file, Markdown export, and repository upload follow the template that is selected.
- Custom ReadMe: Custom ReadMe trims the README text to the lines you pick from the selected template. Generate, Anonymous, JSON, and repository upload still use the full template.
- Save as draft: A small Save as draft button under the action buttons downloads the form as JSON without requiring any section. The file name includes the local date and time. Readme Import / Draft Import loads that file and fills every form field. Drafts contain form information only and do not include API tokens, repository credentials, or private URLs.
- Generate menu: Generate ReadMe File, Custom ReadMe, Anonymous ReadMe File, and JSON/MD File are collected in one menu at the bottom of the form. The button itself still creates the standard README. The arrow opens the other three choices. Send to Dataverse and Send to Figshare stay beside that menu. Each send button shows Connected or Not connected, and the generate and send buttons are the same height.
- Description character count: A small counter under Description of Dataset shows how many characters you have written. It updates as you type, including in the larger editor, and when the field is filled from an import.
URGE V1.6
- JSON/MD File: The previous “JSON File” button is now labelled JSON/MD File. Clicking it opens a format chooser so you can download either structured metadata (
dataset_metadata.json) or a Markdown README (README.md) for GitHub, GitLab, and Zenodo.
- Dataverse connection indicator: The “Send to Dataverse” button now shows a small connection status under its label. A green light with “Connected” appears once an API token and DOI have been entered and a connection to Dataverse has been successfully established; otherwise a red light with “Not connected” is shown.
- Live status: The indicator turns green right after the dataset is fetched from the Dataverse API, and resets to red whenever the API token or DOI fields are edited, so it always reflects the current connection state.
- Feedback: A Feedback link in the sidebar opens a short form. Each benefit is rated from 1 to 5. When every item is rated, URGE prepares an email to forskningsdata@usn.no in your own mail program. The answers are not stored on the server.
- Data-specific information from files: Under Data-Specific Information, Generate from data file(s)… drafts that section from tabular files. If the dataset is a Dataverse draft and Dataverse has already processed the file, URGE uses variable-level metadata only; the data file itself is not downloaded. Otherwise you can choose a local copy. It is read in your browser and is not uploaded. Supported local formats: CSV, TSV, Excel (.xlsx, .xls), SPSS (.sav, .zsav), and Stata (.dta). Up to 5 files, 50 MB each.
- What the draft includes: Variable names, types, value labels, missing-data codes, and date formats. Values URGE has inferred are marked for you to verify. Descriptions, units, and data sources still need to be completed by you. Free-text values and identifiers are not copied into the README. You review the draft, then append it or replace the existing text (replace asks for confirmation).
- Larger editor: Long text fields (dataset description, methodology, file list, data-specific information, and sharing) have an expand button that opens the same text in a larger editor. Closing it writes the text back into the form.
URGE V1.5
- Sidebar navigation (accordion): The right-hand section menu is now a Bootstrap accordion. Only one panel stays open at a time (
data-bs-parent). Opening a panel scrolls the main page to the matching form section; scrolling the page still updates section context via scrollspy, using a hidden navigation target so the visible UI stays the accordion.
- Section checklist & status LEDs: Under each menu section, a compact checklist lists the relevant inputs and textareas. A small dot shows completion: green when the field has content, red when it is empty. Clicking a row scrolls to and focuses that field.
- General Information checklist: Includes Title, DOI, a “Contact Information” subgroup, Surname/Name, Institution, Email, ORCID, and Description of Dataset. The Import panel shows a short note when there are no checklist fields in that section.
- Consistent checklist across sections: Methodology, File Information, Data-specific Information, and Sharing use the same LED-style checklist for their long-text fields.
- Live updates: The checklist refreshes on typing and when the form is filled programmatically (e.g. JSON/README import, Dataverse fetch, dataset selection, sharing “add text” / fetch actions, insertable snippets).
- Section anchors: Sidebar sections align with the corresponding headings in the main form (Import through Sharing).
- Sidebar styling: Accordion header buttons no longer use separate borders or drop shadows; the outer menu card keeps its existing shadow. Checklist labels use lighter, smaller typography for a minimal look.
- Technical: Event listeners for checklist refresh are attached to the main content container so fields inside nested markup still update the LEDs reliably.
- Other Details removed: The placeholder “Other Details” block and its sidebar entry were removed; Sharing is the sixth and final navigable section.
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
Privacy Policy