DOI duplicates, Item type mappings, and Processing statistics | IRUS | Jisc
Skip to main content Jisc logo
  • About
    • What is IRUS?
    • Service description
    • Participants
    • Policies
    • Users and uses
    • Case studies
  • Support
    • Guides
    • Webinars
    • FAQs
    • Glossary
  • Updates
    • Announcements
    • Release notes
  • Participate
    • Join
    • Implement
    • Expose identifiers

IRUS

  • Report
    • Custom Platform Master Report
    • Combined R4/R5 Platform Report

    • Custom Item Master Report
    • Individual Item Report

    • Item statistics by ORCID
  • Visualise
    • Top Items
  • Manage
    • DOI duplicates
    • Item type mappings
    • Processing statistics
  • Embed
    • API
    • Widget
    • Widget demonstrator
  • Service
    • IRUS
    • IRUS-UK
    • IRUS-ANZ
    • IRUS-US
    • IRUS-OAPEN

    • IRUS-UK (Legacy R4)
    • IRUS-ANZ (Legacy R4)
    • IRUS-US (Legacy R4)
  • IRUS
  • Support
  • Guides
  • DOI duplicates, Item type mappings, and Processing statistics

DOI duplicates, Item type mappings, and Processing statistics

The Manage area provides access to reports to help you improve metadata management in your repository using IRUS metadata.

DOI duplicates

The relationship between research output items and DOIs should be straightforward. Each output item should have a single DOI assigned to it and each DOI should point to a single output item. If more than one DOI is assigned to an item this can cause issues and effectively lower the usage count of an item.

To try and help you manage this we provide the DOI duplicates report. This is a simple report to run, showing items with duplicate DOIs in a selected repository. You may find this useful to assist in tidying up of any duplicate entries that are shown.

Item type mappings

Using the Item type mappings report means you can view how your items have been mapped to the IRUS item types and even drill down to individual item level detail.

In IRUS we manually map the 'Source Item Type', that comes from an individual repository, to one of the IRUS Item Types.

We select the most appropriate single item type, even though the host repository may have chosen multiple item types.

The source item type is retained and not altered in any way in case any future amendment in mapping is required.

The process for mapping item types is detailed in our Item types policy.

Processing statistics

The Processing statistics report shows details of how events (tracker messages received) have been processed into statistics presented in IRUS.

It shows the results and explains the terms we use in breaking down the figures from incoming events, through processing, and finally into countable events.

There are options to view monthly or daily stats.

This report equates to the old 'Ingest stats' in IRUS R4.

Contact
  • help@jisc.ac.uk
Useful links
  • Accessibility
  • Cookies
  • Privacy and your data
  • Twitter : @irusnews