Pure release 4.11.0

General improvements, Country-specific improvements, Next release

Smarter than ever: Better automatic author matching during publication import
Yours or mine: New claiming and disclaiming of authorships
Finally out of beta: The all-new Reporting Module
Many matches, but what is important: Rating in search results
Pure in the role as a repository: Now with HANDLE.NET integration
Have it your way: Configurable online import sources
Refuse thy name: Journal renaming with Sherpa's RoMEO
Spacious: Maximise the main column in workspace
Handy: Content listings with actions and links
Programmer's delight: Improved Web Service

Pure's person matching engine has been improved, which results in better and more precise matches between imported publications' authors and academic staff in Pure.

As part of that, it is now possible to configure how organisations are treated. Three options are available for system administrators to choose from:

Ignore organisations: Matches are based only on person names
Use search index: Matches are based on the search index for academic staff
Define organisations' names and post codes: Name and postcode is part of matching

The latter option allows system administrators to specify name variations and a range of postcodes for the main organisation. The specified names and postcodes will then be used in Pure's algorithms when matching authors to staff members.

Finally, matching is now performed in the background, which improves the user experience; a progress bar shows the matching process, which is relevant when importing publications with many authors.

Personal users now have the ability to claim and disclaim authorship of publications.

If a publication does not include the user on the list of authors, as it should, the user can easily notify the relevant editor with a single-click, and ask that he or she be added as a contributor with the appropriate role - usually the role of an "Author".
Similarly, if the user has been placed on an author list by mistake, the user can now disclaim the publication, by sending that request to the relevant editor in the same way. The editor receives notification in both cases, and can overview all claims and disclaims in a interface that was designed for the purpose. Special editors can be appointed to handle this task exclusively, but the task can also be given to exiting editors in Pure, both global editors and editors at specific departments.

The new reporting module was introduced some releases ago and is now out of beta. It replaces the old reporting functionality.

Users can produce comprehensive reports on data in Pure - one example could be a periodic departmental report showing development in departments' outputs, projects, funding, staff, etc. Grouping and sorting can be added, showing for example awards by year or by staff. Anything can be highlighted; e.g. top ten awards, top funders, most successful applicants, most cited publications or authors, etc. Results can be calculated from any kind of base data; e.g. application success rates over time calculated on individual award data. Graphs (such as bars, pies, lines) can be used to illustrate calculations; e.g. a graph illustrating the development in cited outputs vs. non-cited outputs over time. These are just examples.

A new layout selection called Raw Data Spreadsheet has been added, allowing any data and calculations to be output directly to Excel or similar.

Listing, Table, and Raw have new ordering that includes 'direction'.

Top results have been added to Table (analysis).

All filter description templates have been updated along with new versions of the editing interfaces.

Information about when the report definition was created and last modified has been added. Also, a new message appears when the report has any changes.

The reporting module's "organisational unit" selector has been replaced. The new version has a split-view with search to the left and selection to the right. To that, search/filtering has been added for easy limitation when setting organisation criteria, and a new dynamically loaded hierarchy has been created to avoid long load times in case of many organisations.

For a complete overview of all reporting capabilities, a new page called "Report documentation" has been added to the administrator tab under "documentation". All filters, groupings, projections (columns) and functions are displayed for each content type.

By default when searching in Pure, search results are now sorted by rating with the most important result on top.

Over the years, Pure has had repository functionality added regularly. This has been an owner-driven process that gradually has made it possible for institutions with that interest to use Pure instead of a strand-alone repository; where the norm has been and probably still is to use Pure in combination with a repository system. Version 4.11.0 sees the latest addition of such repository functionality, namely the ability for Pure to integrate with HANDLE.NET in the same way that several dedicated repository systems do. Integration with repositories is still available as before, of course, but we hope this new addition will make Pure a better solution for those who use or want to use Pure as their institutional repository.

System administrators in Pure can now configure which online import sources are available for users, and they can make all relevant settings for each source. The order in which sources appear on users screens can also be specified. This is a huge advantage to previous versions of Pure, where Atira staff had to configure each instance of Pure to owners' specifications and distribute these settings with scheduled releases.

Existing journal titles in Pure can be compared with journal titles in Sherpa's RoMEO service when journal data is synchronised anyway. It can be turned on or off by system administrators in Pure. If turned on, differences in capitalising and spelling will be logged. All logged data can be exported to a text file as basis for manual changing of journals titles where necessary.

A small improvement of Pure's user interface is the ability for single-click removal of the sidebars. It can be done at any place in Pure with any role. The idea is to instantly provide more screen property in situations where the screen's overview contains much data.

Content listings in Pure have been updated to a simpler and cleaner look. Each content item in a list shows a new "gear" icon, where all contextual actions are available for that piece of content. To that, internal authors are shown as links. If clicked, a popup window reveals the available information about that author.

Pure's Web Service API has changed. Element names as well as namespaces have been aligned and now adhere to a well-defined internal naming convention. For model-oriented operations (e.g. GetPublicationRequest) customer-specific versions have been added. UK customers will see new operations GetResearchoutputBaseUk and GetResearchoutputCustUk_Customername_ for example (see below). The stable version of the SOAP and REST Web Service interfaces was changed on the following points:

1) It is now possible to limit a search for a publication by specifying the source and/or source_id with an <externalid> element.
2) The XML returned from content listings is extended with a full URL to the content if that is available - this is relevant when a PurePortal-solution is deployed.
3) Previously, role information was part of the workflow state output, but that is no longer the case.
4) Output of external organisations was extended with the additional XML given in this schema fragment:

<xs:complexType name="ClassifiedExternalOrganisationListType">
<xs:sequence minOccurs="0" maxOccurs="unbounded">
<xs:element name="externalOrganisation" type="externalorganisation:ClassifiedExternalOrganisationType" />
</xs:sequence>
</xs:complexType>
<xs:complexType name="ClassifiedExternalOrganisationType">
<xs:sequence>
<xs:element name="externalOrganisationType" type="core:ClassificationType" minOccurs="1" /> <xs:element name="externalOrganisation" type="externalorganisation:ExternalOrganisationType" /> </xs:sequence>
</xs:complexType>

Where do I find a particle accelerator: Equipment and facilities (UK)
REF2014: More functionality added (UK)
Top secret: Better handling of confidential content in Pure (UK)
Automatic: Exhibition of research output by publication state (UK)
UK programmer's delight: Changes to the Web Service API (UK)
Editing synchronised content: Editable participants on synchronised projects (UK)
Data model changes: Update of publication types (DK)
More data model changes: Improvement of verbal contributions (DK)
DK programmer's delight: Changes to the Web Service API (DK)

A new type of content has been added to the UK datamodel: Equipment and facilities. It has been part of CERIF for a long time, but has only recently been requested by UK institutions. It has now been added to Pure for all UK owners.

Implementation of the new type in Pure covers all areas of such an implementation including for example incorporation with Pure's Web Service API and all reporting facilities. The latter allows equipment to be reported by certain criteria (e.g. listed by department, country, etc.) and to function as criteria (e.g. list all institutions with a particle accelerator). Equipment can be linked with research output, projects, funding, activities, external organisations, and other equipment. Editing of equipment is available for administrators and users with the new "Editor of equipment" role.

Note: The new content type contains a classification scheme called "Research Technique". It is empty by default and will not be shown in the editor. If the classification scheme is to be used, values must be added to the scheme. System administrators can do all this.

Noteworthy additions to the REF2014 module are:

1) New summary pages for REF1, REF2, and OUA
2) Reworked editors for REF2 and REF1
3) REF1b have been introduced with own editor and workflow
4) Selection of candidates for REF2 have been changed
5) Research Output can now be locked when selected for REF
6) Bulk change script for REF1

Summary pages have been introduced for REF2 and for Units of Assessment, and the summary page for REF1 has been reworked. It is now possible to sort on the various columns in the summary page for REF1 and REF2.

REF1a/c and REF2 editors have been changed. The REF2 editor is now capable of showing and hiding fields depending of various states; e.g. Selection Status. The renderers for REF2 also reflect this. The REF1a/c editor now shows the number of outputs to be returned without a penalty, and it is possible to attach a REF1b.

The field "In post throughout" is no longer available. Instead it is calculated based on the associated person's organisational affiliation combined with possible override values.

Further, the field "Entry into academic profession" is no longer available on the REF1a/c editor. It is instead calculated on the REF1b editor combined with possible override values. REF1b must explicitly be created for those REF1a/c that need it.

REF1b individual staff circumstances have been introduced with their own editor and workflow. This can only be edited by administrators and by Editor of REF1b REF2014 users. The editor shows how many outputs should be returned without a penalty, this value is also shown on the REF1a editor.

The selection of candidates for REF2 has been changed. It is now also present on the personal overview page that personal users see when they login to Pure, if they have a REF1 staff. The submitter can give the candidate a rating between 0 and 5. It is possible to push notes to the submitter by adding a note in the REF2 editor (it will not be shown to the submitter on the selection tab. The submitter can then reply to the comments by adding another comment. Such communication is supported by emails as elsewhere in Pure.

Research Outputs that are selected for REF can be locked. It is possible when the corresponding REF2 object is in the workflow state "REF2 checking underway" or in the state "REF2 Confirmed". When locked, no users can change the output; not even administrators. If the output must be changed, the REF2 object must first be set to another workflow state. It is possible to configure whether research outputs should be locked as described. System administrators can configure it.

Finally, it is now possible to bulk-change eligible, submitted, and category values for all staff that have defaults values.

Pure's role/right model and content access strategies will normally handle who can create, edit and see content. In addition, it is possible to mark content as confidential. This is now possible for research outputs, projects, and funding. It will make that content accessible only to participating users, editors and administrators. Confidential content is not accessible from Pure's Web Service API, over OAI-PMH, in PurePortal, or via Z39.50.

The visibility of a research output can now be configured to depend on publication state. Administrators can for example specify that outputs in the state "Pre-published" are accessible on campus only, while outputs in the state "Published" are publicly available; i.e. available via PurePortal, via Pure's Web Service API, via OAI, etc.

When a state has been set on the output, the visibility of the output will automatically be set accordingly, but it can be changed manually if need be.

The Student Theses type is now available from the Web Service API with the new operations "GetStudentPublications" and "Getkeywordsfromstudentpublication". Similarly, the Equipment type was also added with the operation "GetEquipment".

It is now possible to add and remove participants on projects that are retrieved from a source system such as a finance system.

The following limitations ensure data integrity: The participant role selection is limited to not including Principal investigator and Co-investigator. For participants that are synchronised only fields that are not synchronized can be changed, and it is not possible to remove such participants.

Please refer to the Danish release notes.

Please refer to the Danish release notes.

Please refer to the Danish release notes.

Pure 4.11.0 was released on 1 November 2011. The next feature release will be version 4.12.0, which is due on 1 February 2012. It will include significant new features, both general and country-specific.