Personal overview, Researcher profile, Own applications and awards, Add and edit own outputs, projects, and esteem, Publication Import with Author Matching, Scan for Publications, Search, filter, list, and export, CVs, Trusted users, Favourites, Confidential content, Display content relations graphically
The researcher's main screen offers an overview of all personal content including Publications, Activities, and Projects. Any piece of content is immediately clickable for full details. The main screen also provides overview of tasks, messages, favourites, curricula and recent actions, and gives access to Pure's online help system. With the UK data-model, Impact Cases and REF output candidates can also be monitored by researchers from here.
The individual researcher can choose to make his or her profile publicly available in whole or in part.
The profile itself holds information such as basic name- and contact-information, name variations, titles, job functions, profile photos, scientific areas (narrative and by controlled keywords; please also see Classifications), attached documents, and more.
All the researcher's content is shown on the profile's relations-tab: Research outputs, grant awards, projects, esteem, organisational affiliations, funding bodies from which awards have been won, journals in which he or she has published, etc.
The profile includes user-definable fields for purposes such as Previous employer, Other work, Consultancy, or Teaching.
Finally, besides Pure's own unique identifier, the profile can also be made to hold Thomson-Reuters' ResearcherID and Scopus' Author ID as well as an ORCID identifier.
Researchers can add and edit their own outputs, projects and esteem. They can also have clerical staff do this; either by setting the workflows for this or by using the Trusted users functionality.
Projects are usually created automatically in Pure by integration with one or more back-office systems, but researchers or clerical staff can edit and enrich them; adding postgraduate students, for example, relating publications to them, etc.
Esteem can be added and edited by researchers or clerical staff over time as the portfolio builds up.
Finally, outputs can be added manually or imported. When adding outputs manually, a template is available for each type of output, please see the screenshots below. Users can change templates mid-submission if necessary, which avoids any unnecessary loss of data.
Templates for manual submissions are easy to use. One example is that in large parts they are populated by use of drop-downs fields, lookup dialogues, and similar measures, which also furthers data quality. All look-up dialogues are user-centric. They will show the user's own content in any given situation; own previous co-authors and PGRs, own projects, or own previous external collaborators, for example.
This saves time and effort compared to searching or browsing the entire database. A switch makes it possible to search and browse the full database if that is desired.
Another example of the editors' ease of use is, that context sensitive help offers individual descriptions of each field in each template:
NOTE: Higher-level users such as administrators can also add and edit content.
Researchers can overview own grant application activities: Pre-application cases, pending applications, awards, and rejections. Each data item can be clicked for full details. Importantly, other researchers and other staff without special rights will only see the awarded applications.
This functionality is possible by dynamic integration with award management systems such as Agresso Award Management from UNIT4 and other systems from other vendors.
Researchers, clerical staff or librarians can import outputs from a growing number of online sources, please see the table below.
Automatic author matching is part of this functionality: an algorithm analyses certain variables to make the right match between the authors in the import-record and the corresponding personnel in Pure; typically coming from the HR system. In addition to that, external authors and institutions already in Pure will also be matched, and if they are not matched, they are created automatically. The same is true for Journals and Publishers.
Such algorithmically proposed matches can be changed by a single click if they are not correct, please see the screenshots below. When matches are made between imported authors and Persons in Pure, proper author-person-organisation relations are created as prescribed in CERIF.
Publication Import with Author Matching supports the following sources, but sources are added continuously, so please enquire:
Web of Science
Journal and publisher information is imported too; title, ISSN number, issue and serial number, publishing date, pages to and from, and more.
Fulltext is imported automatically in the cases where it is available from the source - that is the case with ArXiv, for example. Where fulltext is not available from the source, the researcher, clerical staff or library staff can add it to the publication record in Pure. One or more fulltext items can be attached to the record and classified as appropriate. Fulltext attachments can be set for public availability, for availability within campus, or for no public availability. Availability is set independently of the bibliographic metadata, which allows metadata to be publicly available without the fulltext.
Embargo dates can be set for attachments' public availability, they will then be enforced by Pure as appropriate.
All settings concerning public availability are enforced in Pure itself, in PurePortal, in Pure's exhibition interfaces (Web Services and OAI), and in whatever repository system is set up with Pure; DSpace, ePrints, FEDORA, Equella, etc.
The workflow for publications and other outputs can be set to include a step for librarians to handle or validate fulltext, but Pure's repository integration can also handle this automatically. This means that researchers, local clerical staff, or library staff can attach fulltext and validate as appropriate.
Relations between imported authors and Persons in Pure exist thanks to the automatic author matching, but relations to more personnel can also be made if necessary. A relation can also be made to the project that the publication came out of, and to the grant it stems from. All new relations are made in look-up dialogues. Look-up dialogues are by default limited to the researcher's own co-authors and projects but he or she can set them to provide all Persons and Projects if desired.
If the same publication exists in multiple sources, it can be imported from each such source and the resulting publications can be merged. It can be chosen which parts of which publication-instance to use; the abstract from WoS, the author-list from Scopus, etc. The result is one, unique publication in Pure that comprises the best parts from each source.
Finally, the researcher can decide if the imported publication should be publicly available, or if it should have limited availability.
NOTE: Requires the Self-Import module.
NOTE: Publications can be related directly to REF impact cases upon import or later, which requires the REF2014-module. This is only relevant within the UK.
This feature offers to automatically scan a number of online publication sources for items that might belong to the researcher. The result is provided in a list under "My personal tasks". Scans are based on variations of the researcher's name and his or her organisational unit's name.
Researchers choose if they want to use Pure's Scan for Publications feature. The setting is made on their profile page, where they can also modify the variations of their name used per source.
All sources that are support by the Self-Import module are available. The researcher can choose the relevant ones.
Scans are performed by regular intervals set by administrators.
The list with results allows researchers to import publications by a single click on "Mine, import" and to discard publications by clicking "Not mine, remove". Pure remembers discarded publications and will not show them again to the same researcher. This log can be reset.
NOTE: Please also see Administrating publication scanning under Library functionality for the manager-side of this functionality.
NOTE: Requires the Self-Import module.
Pure's Search-, filter-, list-, and export-options provide easy-to-use yet powerful content navigation for researchers and other users.
Researchers can search among Research Output, Activities, Projects, Grant applications and awards, Impact, and Press clippings. Users with more rights can search more broadly.
A filter limits users to own content by default, but this filter can be switched off by the researcher if he or she wish to search among all Output, Activities, and Projects in Pure; for the purpose of finding co-applicants, for example. Users can also filter on Time period, Output type, Organisational Units, and more, and filters can be combined: specific output types from a specific organisational unit, for example. Searches can be performed when a filter is active, and users can save filters for reuse in other situations.
The result of any search- and/or filtering operation will be shown as a list, and users can immediately export any list in one of several formats: PDF, Word (.docx), Excel (.xlsx), HTML, RIS (Reference Manager), and BibTeX.
NOTE: With the UK datamodel, Impact Cases can also be searched.
Researchers can use Pure's CV functionality to create CVs for different purposes: one for different funding bodies, one for students, one for the web profile page, etc.
CVs can hold content from Pure about the researcher: Publications, Projects, Grant performances, Activities and Esteems, Co-authors, etc. The user only needs to add a section, specify what content it should hold - e.g. publications - and choose certain setting for that section. In addition to such content-sections, researchers can also add free text sections and headlines in order to form a complete CV including narratives.
Sections with content will automatically be updated whenever new content is added to Pure; for example a new publication. This ensures that CVs are always up to date when they are printed. CVs can also be published online on PurePortal. Here, the content sections will also be updated automatically, when new content is added to Pure. The user is notified when a CV has been updated automatically (the yellow notification in screenshot 19 above, SCR.4.10.0.019).
Further, it is possible to make certain settings for sections with content. A section showing publications, for example, can be set to only show specific types such as peer-reviewed articles. Sections can also be set to "Static" if the researcher wants the section to show certain outputs, projects, or esteem regardless of new additions.
Finally, CVs can be exported to Word in native .DOCX format, which makes it easy to further edit and layout the CV if desired. Exporting to PDF is also an option, of course.
This ability to manage CVs and print and publish CVs online was requested by researchers, and it has become an important part of Pure's value-proposition to researchers.
NOTE: Requires the CV module.
NOTE: Publishing online requires PurePortal.
Researchers can let other users carry out tasks for them in Pure.
This facility is used when researchers want clerical staff or other supporting staff to carry out tasks in Pure: any task to the first user will automatically be redirected to the trusted user. It is also useful in cases of annual leave, maternity leave, sickness, or travel.
Together with the flexibility of the workflows in Pure, this feature ensures that working with Pure can follow the business processes that already exist at individual institutes and departments when that is desired, rather than introducing new ones.
Researchers can make any item a favourite - a Person, a Publication, a Project, etc.
Anything can be marked as a favourite by a simple click on the always-available star icon. Once something has been marked this way, it will be added to the user's collection of such preferred content. Here, a short, graphical overview of all favourites offers single-click access to each item. Favourites can also be exported in true reference formats; APA, CBE, Vancouver, Harvard, etc.
This small feature for creating temporary collections of data items was requested by researchers using Pure for everyday work, and it has been widely adopted since.
Researchers and other users with sufficient rights can mark content as confidential.
This is possible with a researcher's Grant applications and awards, Publications, and Projects. A researcher can, for example, mark his or her publication as confidential, or a PI can mark a project as confidential. Users cannot mark content confidential which he or she does not have ownership of; one researcher cannot mark another researcher's publication confidential, for example.
Confidential content is only visible to the users that are associated with the content, relevant editors and highest level administrators.
Please also see Rights management and access delegation under Tech.
Researchers can view all of their relations to other content graphically - relations to grants, projects, outputs, external collaborators, and so on. Please see the screenshot below.
The Dashboard is a white space where users can add Widgets as they like from a wide selection.
A widget is a small graph or text-based piece of information that shows a resume of specific data from Pure. There are widgets such as "Top ten cited researchers", "Top 10 most cited research outputs", "Top 10 esteem types", "Activity types by year", and so on. Widgets show their information in realtime, and they offer the option of drilling down into the underlying data.
Users can set up their dashboard with those and as many widgets as they like. This way, the dashboard offers a personalised overview of whatever information about the organisation's research affairs is important to individual users from their organisational position; researchers, PIs, department managers, and research support offices, for example, have very different information needs.
Data access rights are controlled per users in the same way as reporting. Users cannot use the dashboard to access data they do not have appropriate rights to.
Finally, widgets, which hold limited resume-style information, offer the unique option of turning into a report at the click of a single button. The report can then be set to include fuller details about the specific area.
Research managers can use Pure's Reporting facilities to report on content in Pure. This is true for all types of research managers; primary investigators, managers of institutions and departments, top-level managers at faculty or institution level, and special-area managers such as REF-managers or staff at research support offices. Reporting can be about any type of content in Pure: Publications, Projects, Activities, Organisational Units, Persons, Journals, Publishers, External Organisations, Users, Impact cases, and so on. Further, reporting can represent content in four different forms:
A list of content; grants, projects, publications, etc. Lists can be filtered, grouped and sorted, and a maximum number of items can be defined.
Tables with a defined Y- and X-axis and numerical representations of content
Mathematical operators representing the results as text or as matrixes in tables (see above) - e.g. the percentage of successful grant applications per department normalised by FTE
Users can choose to represent numerical results as pie charts, bar charts, and progression charts
Each report can contain multiple lists, tables, analysis and graphs - they will be represented as multiple sections in the finished report. An example would be that one report could include a) a list of Persons from a specific Organisation, b) then a table showing publication types by authors, c) then an analysis of citations per author over time, and d) finally a graph showing peer-reviewed publications versus non-reviewed.
Detailed filtering criteria can be defined for each list, table, analysis, or graph: Citations can be used as criteria when creating a list of publications, for example, the number of research students can be used when calculating a number of researchers, or publication types can be used when creating a graph about output from a specific organisation.
Further, lists and analysis can be grouped differently. A publication list can for example be grouped by Year, by Authors, or by Organisation. In addition to that, mathematical functions can be set for analyses. All options for filtering, grouping, and setting functions are presented to research managers, when they create the report.
Research managers can also set the formatting for certain content type. For Publication lists, for example, you can choose HARVARD, Vancouver, CBE, MLA, and others.
Reporting can be output in the following file formats:
General output format used when distributing reports automatically to recipients
For viewing on-screen, for pasting formatted content into other applications, etc.
Native Word format, used for working with the reporting result in Word, OpenOffice, Pages, etc.
Native Excel format, used for working with the reporting result in Excel, OpenOffice, Numbers, etc.
A report can be scheduled to run at a specified date and time (please see screenshots above). It can also be set to run with regular intervals; weekly, monthly, quarterly, etc. Further, a list of e-mail recipients can be set up for a report, which facilitates automatic distribution of the report when it runs.
Reports can be shared: Users at one institution can save reports as files and send them to users at other Pure-using institutions.
Finally about security, reporting is subject to Pure's Roles/Rights model and content access strategies. This means that users will only have access to run a report if they also have sufficient access to the content that the report would include. This is checked before the user even sees the report: Users will only see reports they can run.
Research managers can use Pure's reporting facilities to examine the institution's research affairs by different performance indicators:
Grant application success rates
Difference between applications and awards in percentage/number and percentage/volume for a selected period of time and per organisational unit, researcher, discipline code, funding body, etc.
Grant application and award volumes
Volumes of applications and awards in numbers and currency for a selected period of time, per organisational unit, researcher, discipline code, and funding body. Volumes can be normalised by FTEs for internal comparisons between organisational units.
Numbers of collaborations per organisational units for a selected period of time, types of collaborations, collaborations by discipline codes and nationality codes, numbers and types of outputs related to collaborations, percentage of grants related to collaborations, etc.
Research outputs statistics
Numbers and percentages of outputs by types, discipline codes, internal authors and author rankings, peer review status, relations to events, relations to projects, relations to grants and funding bodies, publishing status, etc.
Article citation numbers
Journal articles by citations - many forms of querying are available, many forms of statistical expressions are available.
Journal impact factors
Articles by the impact factors of their journals - many forms of querying are available, many forms of statistical expressions are available.
Innovation activities, commercialisation
Lists, numbers and statistics about spin-outs, patents, licenses, private sector collaborations, etc.
National and international awards and prizes, presentations of keynotes at international events, editorial and refereeing work, elections for learned societies, juried selections of works for exhibition, performance, recording, or screening, reviews of artworks, etc.
Can be expressed as numbers of, by organisational unit, over specified time periods, normalised by FTE for internal comparisons.
PhDs and equivalent research doctorates and research master's degrees are recorded and related to supervisors. This allows reporting on volumes and growth of such doctorates by department, as well as reporting on completion rates normalised by FTEs.
Post-graduate students statistics
Developments in the numbers of post-graduate students can be studied by organisational unit (normalised by FTEs), internal units can be compared, and reports can be on specific time periods.
Research active academics numbers
Basic numbers of research active academics are available from Pure in various ways, for example by association to units of assessment (UK) or by other local or national subject area taxonomies or other classifications.
This allows reporting on the development of percentages between research active and non-active academics including cross-departmental comparisons normalised by FTE or grant volumes, for example.
Fulltext download numbers
By output type, discipline codes, etc. By organisational units or individuals, over specified time-periods, normalised by FTEs for internal comparisons
NOTE: Citation and impact factor data from a subscription service such as Thomson-Reuters' Web of Knowledge (including Web of Science) or Elsevier's Scopus or SciVal is necessary to work with citation-based bibliometric indicators.
NOTE: PurePortal is needed for full-text download numbers.
Grants in Pure hold information like award amount, funding body, applicants, application date, award date, ownership percentages, owning organisational unit, and more.
Grants in Pure are related to projects. When viewing a project, some of the grant information will be visible; award amount, dates, and funding body, for example. If more detail about a grant is wanted, the grant itself can be opened directly from the project, which will provide the full grant details described above.
Grant information will typically come from integration with award management systems but can also come from finance systems, for example.
The result of an import is a rich publication record in Pure with all bibliographic metadata from the source, correct relations to all internal authors, correct relations to all related organisations (e.g. school, institute, department), correct relations to one or more projects, and all primary journal information (ISSN, publishing date, etc.). If the user wishes, one or more full-text files can be added. Also URLs can be added by the user as can Bibliographic notes and additional relations. With the UK datamodel, Impact cases can be added directly at this point (REF-specific feature), and the user can also decide if the imported publication should be publicly available, or if it should have limited availability.
Requires the Self-import module. Please also see Automated bulk imports below for a description of Pure's bulk-import feature. Finally, more information is available in the Pure4 White-paper.
The availability of correctly integrated funding information in Pure allows reporting about grants themselves and related data items such as Research Staff, Projects, Outputs, Organisational Units, External Collaborators, and others.
TYPE OF CONTENT
List grants last 5 years (L5Y) by award volume grouped by organisational unit (org.unit)
List grants L5Y by award volume grouped by funder
Matrix funder (Y-axis) with years (X-axis) showing award numbers
Bar-chart grant volumes L5Y by org.unit
Pie-chart discipline codes by total sum of awards for current year
Progression-chart award numbers L5Y per org.unit (normalised by FTE)
Grants + Projects
List active projects grouped by org.unit sorted by grant volume
List active projects due to complete next 3 months grouped by org.unit sorted by date
Grants + Research Staff
List top 10 awarded researchers with volumes per year for L5Y
List all awarded researchers L5Y with award volumes grouped by org.unit sorted by award volumes
Grants + Outputs
List outputs L5Y grouped by funders sorted by total number of citations
List 10 most cited outputs L5Y with funder information
List all outputs to come from projects sponsored by a specific funder
Matrix org.units (Y-axis) with funders (X-axis) showing total number of outputs
Bar-chart most cited publications L5Y with funders
Progression-chart number of outputs and number of citations L5Y for a specific funder
Pie-chart percentage of all outputs L5Y funded at least 50% by a specific funder
Grants + Organisational Units
List all awards L5Y grouped by org.units sorted by award volume
List top 10 org.units by award volumes L5Y
Bar-chart org.units by award volumes L5Y
Matrix org.units (Y-axis) with funders (X-axis) showing grant volumes/numbers
Grants + External Collaborators
List all projects that includes external collaborators grouped by funder
Pie-chart percentage of funded projects that includes external collaborators
These are only examples. Users can make the reports they want.
Budget information is available on projects.
Budget information will typically come from integration with finance- or costing systems, but can also come from other systems or even spreadsheets. Budgets can be represented on the project in Pure as it is in the source system, or only selected pieces of information can be retrieved. Data values can also be aggregated in Pure.
Budgets on projects can span several years, and they can be grouped into spending categories. Spending categories can be defined on a customer basis - usually an institution will use the same ones that are used in the financial system or other source system; e.g. "equipment", "salaries", "travel", etc.
The availability of integrated project budgets allow reporting on budgets in combination with other data items:
TYPE OF CONTENT
Project + budget data
List active projects ahead of budget based on time/spending ratio
Table active projects showing budget vs. actual spending
Financial information about the actual spending is also available on projects in Pure.
Actual spending is usually retrieved via an integration with the financial system. The transactions are not commonly brought into Pure individually but are instead aggregated into the same spending categories that the budget information is represented in; "equipment", "salaries", "travel", for example. This provides the ability for PIs to run budget-spending analyses directly in Pure without interfacing with the financial system.
The availability of correctly integrated spending data allows project spending reports to be run in Pure:
TYPE OF CONTENT
Project + Spending data
List projects more than 2 months active with no spending
List projects more than 30% active with less than 30% spending
List active projects sorted by budget/spending difference ratio grouped by org.unit
Pure's workflow engine allows content submitted by one user to be enriched or validated by another user. Workflows are an important part of the data quality assurance policy that an institution can employ with Pure.
A workflow can be specified for each content type in Pure - a workflow for outputs, projects, esteem, external collaborators, etc. Pure comes with default workflows that are used by most institutions, but they can be customised to meet individual requirements. This allows the support of existing business processes rather than the introduction of new ones.
One workflow can include as many steps as desired. Pure's standard publication workflow comprises two steps:
Researcher and/or clerical staff
Submitting publication metadata and full-text file/s
Validating the publication metadata and full-text file/s
A variation with three steps is the second most common publication workflow among owners of Pure:
Clerical staff at department level
Submitting publication metadata and full-text file/s
Checking authorship and approving academic info
Validating the publication metadata and full-text file/s
The first example requires academics or clerical staff at department level to add the publication; either by keying it in, by importing it, or by using Pure's Scan for Publications feature. It then requires the library to check that everything is right - e.g. checking that full-text rights have been set correctly or setting these rights.
The second workflow requires clerical staff to add the publication. It then requires academic staff to check that it is right. Finally, it requires the library to validate the submission of metadata and full-text objects.
NOTE: In the first example, researchers can have clerical staff do the submission using Pure's Trusted User feature. In the second example, steps 1 and 2 can also function in reverse. This allows researchers to do the basic submission while clerical staff complete it - this is supported without changing the workflow at all. This suits some departments well, and it allows the same workflow to support different practices at different departments, which is very cost-effective.
Until the first step in a workflow is completed, the user will set the workflow status to "Entry in progress". Nothing will happen yet. When the first step is completed, he or she will set it to "For validation". This will make the publication appear as a task in the user interface of the user or users responsible for the next step in the workflow. They will be notified of this task, by a message in Pure, and via e-mail. E-mails can be sent as a daily, weekly, or monthly digest. Once the next user has completed the task - a librarian setting the full-text rights, as in the first example above - he or she will set the workflow status to "Validated".
Once validated, content is locked and can no longer be edited (administrators can however turn on Pure's re-validation feature, which allows the originating user to update the publication even after it has been validated).
The benefit of workflows is that different users - academics, clerical staff, librarians - can collaborate when producing data and when assuring data quality. Researchers can add the academic details of a publication, that only they would know, clerical staff can complete the submission, and librarians can handle full-text copyright issues that they are best qualified in handling, for example.
Publication metadata and full-text in Pure can automatically be deposited in repository systems. Pure currently works with DSpace, ePrints, FEDORA, and Equella, but please enquire.
Integration with repositories is based on rules defined by repository managers. Rules will for example define which publication types from which organisational units are deposited in which collections in the repository.
Deposit a publication to one or more repositories or to different collections within the same repository
Control deposition by an extensible filter architecture (see table below)
Support of license agreements
Support for acceptance of license agreements by end users through Pure: Licenses are presented for acceptance in Pure when a user deposits a file.
Asynchronous deposition of files in repository systems: The user will not have to wait for a publication to be deposited in the repository after upload but can continue working while Pure silently deposits the publication.
Automatic depositing in repositories can be configured with these filters:
Publications classified as “Science” go into one collection, while economic publications go into another.
Files/publications are only transferred to DSpace when an embargo date is passed.
Publications uploaded to Pure can be marked as having limited visibility (there are several degrees of visibility available).
Articles in one collection, books in another.
Distribute publications to collections based on organisational ownership.
Control the deposit of publications according to the current workflow stage in Pure.
Finally about repositories, librarians or other users can have a dedicated role in Pure itself, by which they can control deposition of full-text and bibliographic metadata in the repository. Repository managers also have rich functionality available in Pure for running reports and statistics on outputs and related full-text. "Most downloaded fulltext" is a new metric derived from this area, for example.
NOTE: Not all features are available with all repository systems, please enquire.
NOTE: Pure's filtering model is easily extended to accommodate specific customer requirements.
These two content types are commonly managed at the library.
Pure is usually set up so that other users such as academic staff or clerical staff can create these objects as needed, but this will invoke a "silent" workflow (transparent to the academic), by which library staff are prompted to check and approve the newly added publisher or journal object.
Pure handles this problem area by offering both preventive and corrective measures. They are equally important:
Duplicate check upon manual entry
Pure checks fields in real-time upon entry. The user is warned and has one-click access to existing items.
Duplicate check upon publication import
Pure checks titles, source ID (e.g. PMID from PubMed or UT-number from Web of Science) upon entry. The user is denied re-import but offered one-click access to the already-existing publications in Pure.
Show duplicates in user interface
Pure automatically shows duplicate data items on the main screen for relevant users
Also match and notify co-authors upon import
All authors are matched during publication importing from Scopus, Web of Science, and other sources. This avoids multiple import attempts, which helps reduce duplicate occurrences.
Duplicate check of journals and publishers upon entry
Journals and publishers are matched upon import. Further, users are warned if trying to manually input duplicate names.
Find duplicate data items
Users can proactively search and identify duplicate items by different criteria
Delete duplicate data item
Users can delete duplicate items. Supported with Journals, Publishers, Publications, and Activities.
Merge duplicate items
Users can merge duplicate items. Supported with Journals, Publishers, and Publications.
When finding duplicates, users will search in a specialised user interface. Facilities are available to specify the search by certain fields, by content types, by time periods, and so on. Users can omit false duplicates, and these will not be shown again as duplicates (this log can be reset).
When deleting duplicates, the user is shown the duplicate sets and can choose which one or ones of the set to delete. Relations to other content from the deleted ones will be moved to the remaining one.
When merging duplicates, the user is shown the duplicate set in a special user interface where he or she can choose which parts of each duplicate will be retained - i.e. the author list from one duplicate, the abstract from another. Upon executing the merge, all relations to other content from all former duplicates are placed on the one unique publication that is the result of the merge.
NOTE: Rights to manage duplicates and to carry out corrective operations are usually delegated to library staff or similar staff with specialised data management skills and responsibility for overall data quality.
Classifications in Pure are fixed values usually displayed in a drop-down dialogue. The term "Classification" also applies to the concepts of controlled vocabularies and other types of taxonomies to be used in Pure - it is all done by use of classifications.
An individual classification - e.g. the value "England" - would belong to a classification scheme. A drop-down list with 20 countries, for example, is a classification scheme with 20 classifications on it. Classification schemes can be hierarchical and there is no limit to the number of hierarchical levels - e.g. "United Kingdom" and under that, "England".
Classifications are often managed at the library. Pure comes with a number of classification schemes out of the box; so-called system classifications. They are factory defined, but librarians can edit all system classifications, and they can create their own all-new classifications; so-called local classifications.
A classic example of classification usage is adding Research Discipline Codes to Outputs, Research Staff, Projects, or Organisational Units, but classifications are also used to classify many other types of content for many different purposes.
Examples are listed below:
CLASSIFICATION USAGE EXAMPLE
Type (e.g. Research, Consultancy, Research Fellowship, Research Studentship, Equipment only, etc.)
Funding programme (e.g. Responsive, Studentship, Tendered, Contract, Directed, Research Priming Fund, etc.)
Publication States (e.g. Published, In Preparation, In Press)
Research Discipline Codes (defined locally or Dewey, Ortelius, etc.)
Status (e.g. Applied, Current, Completed, Awarded, Not Awarded, Pending, etc.)
Research Discipline Codes (defined locally or Dewey, Ortelius, etc.)
Impact nature (e.g. Cultural impact, Economic impact, Public Policy impact, or Quality of Life impact, etc.)
Esteem, e.g. an Award
Type of Award (e.g. Prize, Medal, Election to learned society, Honorary degree, etc.)
Research Discipline Codes (defined locally or Dewey, Ortelius, etc.)
Visibility of profile (e.g. Publicly available, Available on campus, Available in Pure)
Type (e.g. Faculty/School, Institute, Department, etc.)
Type (e.g. Research Funding Body, Publisher, External Collaborator, etc.)
Classification schemes can be hierarchical. There is no limit to the number of levels.
If classification values are changed, Pure will automatically find and replace old values with the new ones in the entire database. This is transparent to the user and takes place without waiting time. The database is then re-indexed.
There can be more than one classification scheme for any area. There can be several classification schemes for "Research Discipline Codes" making it possible to classify things by both a discipline-specific ontology and a broader, general one like Dewey or Ortelius, for example.
Also, Research Discipline Codes can be used on PurePortal to navigate content there; for members of the Press to find experts on specific subjects, for example.
Further, classifications can be used as criteria in reports. A report on grants can be set to include only applications for equipment, for example. This is true for both system classifications and local classifications; the latter being those created by librarians.
Finally, researchers can opt to add self-defined keywords after adding one or more classifications. These so-called "free keywords" can be very specific for the research item in questions in a way that standard ontologies rarely can.
Adding classifications onto various data items can be mandatory or optional, determined by Administrators. This is defined per classification, which ensures the necessary flexibility.
Pure has used the Sherpa RoMEO API to display Open Access information about journals in Pure's user interface since the API was introduced, but additional initiatives aim to increase academics' Open Access awareness and to better support repository managers and Open Access policy makers:
OPEN ACCESS SUPPORT IN PURE
Open Access overview page
All Research Outputs grouped by type. The number of outputs with and without full-text is shown by the four different RoMEO colours. The view can be limited to a specific year and/or a specific organisational unit.
"Open Access” filter for Research Outputs
The "Open Access" filter allows users to limit search results to OA-related items - e.g. all publications without full text but published in a GREEN journal. It is a quick way of finding all Open Access outputs - or all outputs that could be made Open Access.
The journals RoMEO colour is shown in the publication template as soon as the journal is added. The user is encouraged to add the full-text. If the colour is GREEN, the full-text will then go directly online.
RoMEO info in outputs templates
The RoMEO colour is always shown in outputs templates, as mentioned, and the full information can be displayed there with a single click. Users do not need to open the journal to see the full information.
Administrators can manage several settings regarding open access in Pure, including the API address to SHerpa's RoMEO service as it changes and evolves.
Pure's Self-Import module allows administrators - often librarians - to set Pure to perform scans of multiple online publication sources at regular intervals. Researchers can then subscribe to these scans individually, and if they do, all publications that match the researcher's name-variations and the organisation's name variations will automatically be presented to researchers after each scan.
Found publications are presented in a list from which they can be approved or rejected. Rejected suggestions will not be presented to the same researcher again (this log can be reset).
The scanning service in Pure's Self-Import module works with the following online sources:
Web of Science
The scanning service can be set up with the following criteria:
Researchers’ name variations
An unlimited number of variations of a researcher’s name can be used as criteria: E.g. Robertson, Chris; Robertson, C.; Robertson C; Robertson, Christopher; and so on. Pure will create the most common variations automatically, but others can be added manually.
Different name variations can be used for different sources; some for PubMed, others for Scopus, etc.
Organisational units’ name variations
Librarians or other qualified staff will set Pure’s scanning service up with the relevant organisational names for each source to be scanned
Scopus author ID
If researchers' profiles hold the Scopus author ID, it can be used as a criterion when scanning Scopus
Thomson-Reuters Researcher ID
If researchers’ profiles hold the Researcher ID from Thomson-Reuters, it will be used as a criterion when scanning bases on the Web of Knowledge
NOTE: Requires the Self-Import module. Using Scopus author ID and Thomson-Reuter Researcher ID as scanning criteria is subject to individual implementation.
Integration with library systems is facilitated by use of the Z39.50 protocol. It gives users of library systems the option of searching directly in Pure from the library system. This is particularly relevant if there is a strong library culture among students, post-grads and researchers. SRU/W can be supported by request.
It is possible to store metadata about student theses and related fulltext files in Pure. Student theses are related to PGR students and they again are related to their supervisors. This makes it possible to run reports on a supervisor's number of PGRs and theses.
There is no technical difference between student theses and research publications. The difference is between students and researchers; researchers are users in internal back-end systems, students are not. Functionality in Pure therefore allows submission of student theses through PurePortal or through a web form on the institutions own web pages or a student intranet.
Date- and time-stamped certification can be sent to a student administration system verifying the submission, and both metadata and fulltext can be used in reports or made publicly available online.
Students' submissions can be validated in a workflow involving their professors and/or administrative staff at the student administration office.
NOTE: Not relevant with all standard data-models
NOTE: Requires the Student Theses module
A "press clipping" in Pure is a data item with metadata about a press article that was published in the media. It can also contain the fulltext of the press article as text or as an attached document.
Information can be held on this data item about the press article's title, publishing date, publisher, publishing place, and author. A URL can also be used to point to the original press article. It is also possible to add narrative text about the press article - a summary for example.
Certain press agencies in Europe offer a service, by which selected media is monitored for mentions of a specific university and an XML feed is delivered containing all or part of the above mentioned metadata information. Pure's Press Clippings module can import directly from such a feed.
Further, press clippings can be entered manually into Pure by Personal users or staff at a Press Office, for example.
Press clippings in Pure can be related to academics, departments, projects, activities, and esteem. This is important for two reasons:
First, it allows reporting on press coverage by individual academic staff members and by departments. It would, for example, be possible to run a report listing all staff that were mentioned in the press in a specific year, showing a matrix with departments' press mentions over a range of years, or showing a graph with the progression of press mentions over time.
Next, it allows listing on public websites showing press coverage by individual academics and departments. This is true for PurePortal as well as for any other website; other websites would simply retrieve the relevant information from Pure's Web Service API.
Finally, the RSS feature of PurePortal offers push notification of new Press articles to the public.
NOTE: Requires the Press Clippings module
User administration, Organisational Units management, Systems Integration Management, Audit Log, Sessions, Text resources, system messages, and help text, Fulltext file indexing, Caching, Portal settings, Google analytics, Terms and conditions page, Management of online publication sources, Run special jobs, Support user remotely, New user access, Re-indexing, System e-mail settings, Re-validation
Persons (e.g. academic staff) are usually created in Pure by the HR system, with which Pure is integrated , but persons can also be created manually. If integrated with an HR system, a synchronisation job is set up for retrieving staff records from it. Pure is populated with Persons the first time the HR synchronisation job runs and is then kept in sync. Synchronisation jobs can be scheduled by administrators, and they can also do ad-hoc runs.
Persons are not users. For a person to become a user, at least one role must be assigned to a Person. Roles can be added and modified by Administrators. Administrators can also lock a user account, create temporary guest accounts, and do other user management.
Staff coming from the HR system are usually given one role by default, the role of a "Personal User". This role allows the user to add and edit own Outputs, Grants, Projects, Activities, and Esteem, but not those of others. If sufficient information is available from the HR system, other roles can be added automatically, too.
Information from the HR system is not editable and can only be viewed. If users want these details changed, they must contact the administrators of the HR system.
NOTE: See "Systems integration" under Tech for more information about systems integration and synchronisation jobs in Pure
Organisational units are Faculties, institutes, Departments, Research Groups, and so on. These units are usually retrieved by integration with an external system; typically a HR system.
At a university, organisational units can be closed, opened, merged, split, and they can take over each other. These events are modelled correctly in Pure and they are handled without loss of history, which is important for the ability to report correctly and reliably in retrospect and in present time.
In most cases, such events are reflected automatically in Pure as they happen in the HR system: Closing a department in the HR system will simply cause the same organisation to be "former" in Pure. More complex events may not be supported in HR systems, and because of this, Pure offers administrators a feature-set for manual handling of organisational unit structures when necessary.
A good example is Pure's feature called "Taken over by". It allows an administrator to let one organisation take over another. When doing that, all content (e.g. publications) formerly associated with the overtaken organisation will be associated with the overtaking organisation but without loss of the information, that the overtaken organisation once existed and that certain content was produced there. If Pure did not preserve this information, a publication written in 2002 might belong to an organisation founded in 2010, for example, without any clue to how that happened.
Another argument for preserving historic information is the need for retrospective statistics and other reports.
Administrators in Pure can mange the integrations between Pure and other systems.
There is a synchronisation job for each integration in Pure; synchronisation of staff with the HR system, for example. A list of 5-10 integration jobs in Pure would be quite normal and because of that, a Job Management section is available, where administrators can survey and manage their jobs; change run schedules, check that jobs ran as expected, check alerts, start jobs, stop running jobs, or revert Pure to the stage before a specific job last ran.
Further, administrators can set up all-new jobs based on top of existing integrations. Setting up a new import source scan job is possible, for example: When Pure 4.9.0 was released, the update came with new import sources (WorldCat, CrossRef, JournalTOCs, WorldCat).
Also, full synchronisation logs are available for admins, which include all details about individual runs. More technical information about setting up integration with other systems is available under Tech, Systems integration.
Pure is used to make formal data returns in several countries - the REF in Britain, for example. Further, data held in Pure impacts institutions' performance records, rankings, and financial results.
This raises the need for validation procedures to ensure data quality and integrity (as described in Library functionality, Workflows,) but it also raises the need for the ability to establish the origin of content; who put it in, when, who approved it, from what source did it come, etc.
Pure's Audit log facilitates this. All events by all users are systematically saved in the Audit log. Creating, changing, deleting, viewing, or reporting on content is logged together with timestamps and user IDs. The actual change of content is also logged - if a project title is changed, for example, the log will show the title before and after the change-operation was carried out. Data coming from external sources such as citations or impact factors are logged with a source ID and import data, and so on. The entire history of each individual data item in Pure is systematically logged, securely stored, and made available for system administrators or users with special privileges.
Administrators can make look-ups in Pure's Audit Log by search and filter operations. The following filters are available:
Show all events by specific user
Show all events with a specific piece of content (e.g. a grant application, a project, a publication)
Limit to events after a specific date
Limit to events before a specific date
Show all events of a specific type (e.g. all create operations, all delete operations, etc.)
Combining these filters makes it possible to find specific operations by a specific user within a specific timeframe for a specific piece of content. The entire log of an event is stored as XML for ease of access and use of this data; also outside of Pure.
Any user interacting with Pure will do that within a session. Session control is how Pure administrates multiple users and their simultaneous access to data-objects in Pure.
Each session has a unique ID. Administrators can monitor active and past sessions, and they can identify and look up sessions in the Audit Log. Administrators can see the number of active sessions, and they can see the details of each active session: User, Source, Session ID, First and Last request, the IP address of the session's user, and the date and time that session started and stopped.
All of Pure's user interface text can be managed by administrators. The same is true for all field labels. This makes Pure's user interface adaptable to local vocabulary and terminology.
Also, administrators can manage all standard system messages including system e-mails. This ability for system administrators to configure Pure's communication to users allows the user experience to be conformed with existing IT services and concepts on campus. An example would be replacing the standard message "Please contact your system administrator" with "PLEASE CONTACT IT SERVICES ON EXTENSION 7455".
Finally, administrators can manage all help text in Pure. This is true for both the online manual and all context sensitive help text. Administrators can also create all-new help pages.
Text values in Pure's user interface are divided into four categories:
E-mail messages are sent to users of Pure in various situations. The following list is not exhaustive:
When scheduled reports are sent out to recipients
When users are added as co-authors to publications
When users are added as project participants on projects
When tasks are assigned to users
System administrators or other users with appropriate rights can send messages to users in Pure. This is useful in many situations; to let users know about upcoming deadlines, new features, changed business processes, etc.
System messages can be sent to users with one or more specific roles. System messages are co-sent as e-mail as per the individual user’s settings.
A text resource is a piece of text in Pure’s user interface. It can be a field label or any other text in the system’s interface. There are more than 9,000 individual text resources in Pure, not including the help-system.
An error page is shown if Pure is not available to users, for example if IT has taken the server down for hardware upgrading.
Values changed by administrators can be reverted to the default system settings if so desired.
System administrators of Pure can decide if fulltext will be indexed for searching in Pure.
Fulltext file indexing can be switched on by administrators. Word and PDF files can be indexed for searching, and administrators can set a max memory load for PDF files in Mb.
Pure's Graphical User Interface (GUI) can be cached on the server. This will reduce the page-load time that users experience and it will reduce the load on the hosting environment. Administrators can manage GUI caching; turn it on or off, set the max number of cached items, set the max number of domains, and more.
If a PurePortal (see Portal functionality) has been set up with Pure, administrators can turn it on or off and manage certain settings. If PurePortal is turned off, a "no service" landing page becomes visible with standard wording, which administrators can manage.
Both Pure and PurePortal works with Google analytics. The code snippet from Google can be added from within the administrator section of Pure by system administrators.
It is sometimes necessary to ask users to confirm their acceptance of the terms and conditions under which the use of Pure is available at the research institution. This can be the case because of data protection acts, for example, which are common in most European countries and in the UK.
Pure's terms and conditions page can display individual terms and conditions, and it can prompt the user to accept them on the user's first log-in attempt. A session will only be granted if the T&Cs are accepted. Users will only see the page once. The page can be re-displayed if the T&Cs are changed.
Pure's terms and conditions page can be managed by system administrators - the T&Cs themselves can be added, and the feature can be turned on or off.
Pure can import bibliographic and bibliometric information from a number of online sources; Web of Science, Scopus, ArXiv, PubMed, and others. Please see Publication Import with Author Matching.
Administrators can manage the technical side of these import sources. While some sources require no management, others require setting of Web-Service URLs, setting of authentication information, etc. For Web of Science, for example, a search URL can be set, an authentication URL can be set, and the Edition to be accessed can be specified (e.g. SCI, SSCI, AHCI, ISTP).
Custom import of complex data into Pure and export of data from Pure in particular off-standard formats is available as a service from Atira.
Rather than simply performing the special import or export, we will set it up so that system administrators can execute the import or export as a job in Pure as many times as needed and whenever appropriate. The job will not be part of the set of regular synchronisation jobs that run regularly in Pure, it will be a special job that can be run at the administrator's discretion. The benefit is that administrators can choose the right time for the import or export, and he or she can repeat the import or export.
The ability to run such special jobs is a standard feature in Pure.
System administrators or other users with sufficient rights can assume the role of other users. An administrator will then see a 100% copy of the supported user's screen, and the administrator will be able to interact on behalf of the other user. This is particularly useful for short remote support sessions, and it is therefore referred to in Pure's documentation as "supporting users".
When the administrator is done, he or she will leave support-mode whereby the normal administrator screen will reappear.
New users can be granted access to the system by adding the account to the local HR system or by adding an account manually in Pure. If time is critical, the HR system synchronisation job can be run ad hoc, which will cause the user to be created immediately.
Pure's re-indexing feature makes on-demand re-indexing available for administrators from the System settings menu.
Pure's use of e-mail can be set up and handled by administrators; reply-to address, host, port, and a dedicated Pure support e-mail address can be set.
Once content has been validated, it is locked. This is Pure default setting for all content, that has been validated by one or more users in a workflow: Grants, Projects, Publications and other output, Activities, Esteem, External collaborators, and so on.
It is however sometimes practical or even necessary to allow editing of content after validation. For that purpose, content can be unlocked by activating a feature in Pure called re-validation. It will allow content to be edited again, and once saved, the piece of content will automatically be sent through the same workflow it went through the first time - it will be re-validated.
Content for re-validation will not appear to the validator as it did the first time though. Instead, only the changed values will be shown. Only seeing the changed values is much faster than seeing the entire piece of content.
System administrators can turn Pure's feature for re-validation on or off. Many Pure-owners prefer to have it turned off for most of the year, but prefer to set it to on during busy periods when many publications are submitted.
Pure can interface with a number of Thomson-Reuters' services as described below. It requires valid subscriptions with TR.
Citations and impact factors can be imported into Pure and used for bibliometric analyses and other reporting in combination with other data in Pure.
Pure interfaces directly with the two major suppliers of citations-based bibliometric data, Elsevier's Scopus and SciVal products and Thomson-Reuters' Web of Knowledge and InCites products. The table below shows how citation data can be stored on publications in Pure:
Citation data imported from the Web of Science (Thomson-Reuters)
Total number of citations
The source of the citation set
Date of bibliometric processing
The data the citation set was added
Pure can import citations from Web of Knowledge (WoK), which is Thomson-Reuters' (TR) communication platform for the following indexes:
WEB OF KNOWLEDGE INDEXES
The Arts & Humanities Citation Index
The Science Citation Index Expanded
The Social Sciences Citation Index
The Conference Proceedings Citation Index
The Conference Proceedings Citation Index
Social Sciences and Humanities Edition
This can be done in three different ways; from files, together with bibliographic data from the advanced WoK API, and in bulk from the advanced WoK API.
TR's advanced WoK API is available with TR's InCites service. A basic WoK API is available with standard WoK subscriptions. Pure supports this API as standard too, but it is not possible to import citations from the basic WoK API as this API does not exhibit citations.
Pure can also import impact factors from Thomson-Reuters' Journal Citation Report (JCR).
Please note, that Pure's facilities for interfacing with TR-services as mentioned above are developed in collaboration with TR themselves. Only TR-authorised interfacing and data representing is used in Pure. Valid subscriptions with TR must be in place for these facilities to be enabled in Pure.
When someone with a user account for Web of Knowledge logs in, that user can export citations as a file. The citations of this file can then be imported and matched to the publications in Pure. Matching can be done by UT IDs. Matching can also be done without UT IDs - a tool for rectifying wrong matches is provided, so that each citation data set still can be matched to the appropriate publication.
SCR (Importing a batch of citation data sets from Thomson-Reuters' Web of Knowledge in Pure)
WoK's advanced API holds citations per publication per year. When a publication is imported into Pure from the advanced WoK API, citations are imported together with the bibliographical information.
Further, Pure can update citations automatically: If turned on, this feature will automatically retrieve new citation count information from WoK with specified intervals and update individual publications in Pure. Administrators can set the update frequency; one a week, month, etc. Pure logs when publications were last updated, which can be used to prevent reporting on insufficiently updated data.
NOTE: Interfacing with WoK as described and in other ways requires valid subscriptions with Thomson-Reuters. Only users with valid contracts with TR will have access to these and other TR-specific features in Pure.
InCites from TR builds on a customer-specific data set that TR produce per case. This dataset is available for importing into Pure. This is done as a service by Atira, but a standardised tool is available for this, which makes it cost effective.
If this data set is imported into Pure, all publications in Pure that are also in TR's systems will have TR's WoK identifier on them. This identifier is also known as TR's UT-number.
Once UTs are in place on publications, Pure can regularly update citation data on these Publications in Pure. Administrators in Pure can set the desired schedule for updating citations; daily runs, weekly runs, etc. Administrators can also see the result of each update run; how many records transferred, which ones, data and time of last run, etc.
This means that citation data on publications in Pure can be updated regularly and automatically, which again means that reporting on citations becomes more reliable and less time-consuming.
When using citations as a factor in reporting, you have the option of including or excluding data based on "last import" information - so publications are only included if their citations were recently updated. You can also run "house-keeping" reports showing publications lacking citation updating, lacking UT numbers, etc.
TR are now conforming the dataset underlying InCites in a standard format, which makes import easier than previously.
Institutions can purchase files with impact factor data from Thomson-Reuters. The impact factors in this file can then be imported and matched to journals in Pure. Matching is done by ISSN.
The table below shows what impact factor information can be saved on journals in Pure:
Year of impact
The source of the impact factor data
Impact factor data imported from the Web of Science (Thomson-Reuters)
Synchronous Impact Factor
The date the citation set was added
Importing Scopus citations
Pure can import bibliographic records from Elsevier's APIs but not citations, as citations currently are not exhibited in any API from Elsevier. Pure will be able to import citations from Elsevier's API when they are available. It will be standard functionality that will be made available as part of Pure's Self-import module at no additional charge.
We do not currently facilitate import of Scopus-citations from files.
It is possible to analyse content in Pure by bibliometric data. This is possible when citations and impact factors have been imported and matched properly to publications and journals in Pure. Persons - and to some extent Projects and Grants - can be analysed by bibliometrics, because this content is related to Publications and Journals. Comparing publications from specific funding bodies by their citation count would be perfectly possible, for example, as would ranking internal authors by the different metrics.
Pure supports bibliometricians' work with the ability to set up and run Reports, which analyses bibliometric data or cross-references it with bibliographical data and expresses the results in lists, tables, calculations, and graphs. Such analytical results can be exported as PDF or XML, or as data for further use in Word or Excel. Along with this, bibliometricians can use Pure's Search, filter, list, and export functionality for defining and saving subsets of data.
A thorough description of research performance indicators in Pure is available in the separate document called "High-level value of Pure".
Fulltext download statistics is a relatively new metric, but it is increasingly popular.
Downloads are logged for all attachment types: Text files such as Word- and PDF-files, and also binary files such as pictures, movies, and sound.
It is possible to store the download numbers along with information about their source, which makes it possible to differentiate the weighting of downloads depending on the sources.
Further, download numbers can be imported into Pure just as other bibliometric data. Importing is possible from files and from Web-Services or other online interfaces.
Importantly, Pure will automatically add download numbers from PurePortal if a PurePortal-based website exists. They will be stored with "pureportal" as the listed source of origin.
Like other metrics, download numbers can be used as criteria when analysing data in Pure. It is possible to rank publications by their downloads, for example, but download numbers can also be used as a part of more complex and advanced analyses.
Pure supports national research assessment exercises in three countries: The REF in the UK, the BFI project in Denmark, and EWI's FRIS framework project in Belgium.
These programmes serve different purposes and are supported in different ways by Pure. The necessary data model concepts and technical functionalities for each national assessment programme are only available in the relevant country.
Pure supports a full REF return to HEFCE: Outputs, Impact and Environment. Pure's CERIF-based UK datamodel has been extended with the necessary concepts for that. This has been achieved by collaboration with the UK Pure owners, but also by our participation in two JISC projects about CERIF, CRISpool and MICE, and by many fruitful discussions in the euroCRIS CERIF task group, of which we are a member.
Pure's REF module has been released, and it is now in production at all UK Pure-sites, where it is being tested and used for mock returns. Certain updates and additions to Pure's REF module are now being implemented following the release of HEFCE's July 2011 guidance and more will be made following the January 2012 guidance. All such updates are free of charge to all owners of the module and will be delivered as parts of the regular updates in our normal release schedule as per the development roadmap for Pure.
More information about Pure's REF abilities is available in the separate feature article about Pure in the UK and in the separate REF article.
Pure supports EWI's vision of FRIS, the Flemish Research Information Space, by incorporating FRIS-specific content types in a CERIF-datamodel and by conforming with the FRIS project in other ways. In addition to this, Atira supplies consulting and software development for national-level research information infrastructure in Flanders, also related to the FRIS project at EWI under Vlaamse Overheid, the VO.
More information about Pure's FRIS support is available in the separate feature article below:
Pure supports this DASTI-project by incorporating the necessary content types and other BFI_specific concepts in the Danish-based CERIF-model in Pure. Atira has delivered general consulting and development of certain national-level research information infrastructure components in Denmark, which are related to the BFI project. This includes the national research journal service, which is a service exhibiting 250,000+ research journals, which have been rated individually by the 60+ learned societies of Denmark and enriched in other ways, too.
PurePortal is a website for automatic exhibition of content from Pure. It requires no maintenance or management from the institution. Further, it can be deployed instantly. PurePortal facilitates public access to whatever content in Pure has been marked for public availability. Typically that would be researcher profiles, outputs, projects, events, collaborations, etc. Such access is highly relevant for stakeholders like the press, private sector businesses, undergraduates, and other interested parties. PurePortal can also make fulltext available (see Fulltext and Repository functionality). It can do that itself or by pointing to files on a Repository system.
Also, PurePortal will make content available for organic Google and similar search engines, and it will make content available for Google Scholar. This aspect of PurePortal is particularly relevant for the researchers, because high visibility on search engines shortly after a publication's publishing date leads to an increased number of citations. The table below shows examples of content in Pure that can be exhibited online on PurePortal:
Bibliographic metadata can be available online, as can fulltext. PurePortal can make the fulltext available directly or point to a repository.
Publications and all other types of output will link to Researchers, Projects, Events, Organisations, and External Persons and Organisations.
Researchers’ activities can be online. Activities will often be as relevant to the press or to businesses as publications. Also, researchers are usually eager to have full profiles online including activities. Activities will link to Outputs, Researchers, Projects, Organisations, and External Organisations and Persons.
Projects can be made available on PurePortal. All data can be shown, or selected content can be withheld - funding information, for example, or other financial information such as actual spending. Projects will link to Researchers, Organisations, External parties, and Activities.
The institution’s events can be on PurePortal.
Events will link to Researchers, and to the Projects under which they sort; if any.
Researchers (“Persons”) can be shown on PurePortal. The record can be shown in whole or in part.
Researchers will link to outputs, Activities, Projects, Events, Organisations, and External Organisations and Persons.
Organisations can be shown on PurePortal, and as with other content types this can be in whole or in part.
Guests will be able to see all of an organisation’s details, including lists of the organisation’s Researchers, Publications and other Outputs, Events, Press, etc. Each item on each of these lists (for example a researcher on the list of staff members) will be an active link - in this example to the researcher’s profile page.
Organisations will link to Outputs, Activities, Projects, Events, Researchers, as well as External Organisations and Persons.
External Organisations will be displayed, and they link will link to Outputs, Projects, Researchers, Organisations, and External Persons.
External Persons will be displayed, and they will link to Outputs, Projects, Researchers, Organisations, and External Organisations.
If subject keywords have been added to content in Pure, the full list of subject keywords can be browsed by guests on PurePortal.
Subject keywords can be hierarchical. If they are, the full list of subject keywords will also be hierarchical on PurePortal; e.g. “Technical Sciences” “Computer Science” “Application Architecture”.
Guests can browser a pool of subject keywords like this, and when clicking “Application Architecture” as in the example above, the guest will see a list of all content in Pure under that keyword: Not just Researchers within that field, but also Organisations (e.g. “Department of Application Architecture”), Outputs, Projects, Events, etc.
This ability to quickly browse to the university’s entire pool of Researcher Profiles, Departments, Outputs, Projects, etc. is a very powerful feature in Pure and PurePortal. Please also see “Classifications”.
Further, content from Pure remains interrelated on PurePortal. Guests can click a name in a publication's author list and go to that researcher's profile page, for example. In addition, content on PurePortal can be browsed by keywords. Both aspects of PurePortal are useful for guests without an academic background when searching for specific research disciplines.
As mentioned, content on PurePortal will be limited to the content marked for public availability in Pure, but more sophisticated limitations can also be applied. Content can be limited by workflow state and by classifications, for example. In the first case, a publication would only be online when fully validated, for example, and in the second case, publications online could be limited to the ones classified as peer-reviewed, for example. Along with that, workflows can also be set up for manual approval for online accessibility, if desired. This is commonly used for approving fulltext to go on PurePortal (or into a repository system, for that matter).
PurePortal also offers comprehensive search facilities. Both metadata and fulltext (PDF-files and Word-files) can be searched. Search results can be sorted by different criteria and be set to ascending or descending, and searches are ranked by relevance - a match found in a publication's title field, for example, will be ranked higher than a match found in fulltext.
Further, a PurePortal can be managed by administrators. They can set the desired URL for the portal and they can turn the portal on or off. This is done from within the Administrator's user-interface. Similarly, content types can be included or excluded. It is possible to exclude Projects, for example. When excluding a specific type of content, links to that type will not be present on other types of content.
Administrators can also manage text resources for PurePortal. It is done in the same way as for Pure itself, and it gives administrators the freedom to change all values in the graphical Interface of PurePortal including help pages.
PurePortal is available in two versions: Standard PurePortal and Advanced PurePortal. A Standard PurePortal comes free with each Pure license. It can easily be replaced by an Advanced PurePortal, which can be purchased by individual quote depending on the requirements. All features described earlier in this section are available in Basic PurePortal, and in addition to those, Advanced PurePortal includes the following features:
A custom design according to the institution’s own design manual or existing websites - everything can be customised, including stylesheets, colours, proportions, and design graphics.
Dynamic RSS feeds
Guests can subscribe to an RSS-feed for any search they make or to any specific Person, Organisation, Project, etc.
This is a very useful tool for guests to keep up-to-date with a specific researcher’s work, for example, and therefore also a useful tool for the university’s efforts to disseminate research results and profiles.
Diagrams can be used to illustrate relations between objects: Relations between a Person and other persons, for example, or relations between Persons, Organisation, Projects, etc. These are also called “Floating diagrams” because of their appearance.
Any object in such a diagram is click-sensitive: Double-clicking will take the guest to the details for the clicked object. Also, these diagrams can be altered by the guest: Another person can be dragged to the centre, for example to show this person’s relations instead.
Search results can be exported. Exports can be as XML or to PDF-, RTF- and CSV-file. When exporting publications, a reference format can also be set; HARVARD, Vancouver, MLA, APA, and others (may require individual implementation).
Graphs like pie charts, bar charts, or line charts can be shown on PurePortal based on actual data in Pure. That means that the graph will be rendered per session for the individual guest on PurePortal.
It can be used to show real-time status of any numerical data-set in Pure - a graph showing the number of peer-reviewed publications versus non-reviewed, for example, which is updated in real-time according to submissions in Pure.
Log-in by role
Advanced PurePortal can allow users in Pure to login to the Portal with their Pure-user credentials. Such identified users can access content that they would have access to in Pure, but which is not accessible on the portal for outside guests.
This is also referred to at the intranet-functionality of PurePortal.
If the Student Theses module is installed, PurePortal can have functionality for submission of student theses in Pure via PurePortal.
Students can identify themselves manually or be authenticated by an integration to the student administration system. They can add the required metadata about the thesis, and attach fulltext. All data submitted this way will go directly to Pure. Please also see Student Theses.
Refine my search
Advanced PurePortal can be equipped with single-click options for refining searches by a number of factors - e.g. “more by same author”, “more in same journal”, more by same publisher”, and so on.
Advanced PurePortal is based on an extensive technical framework, which was made for customisation. This means that any Advanced PurePortal can be customised to meet local requirements for different graphical design and additional functionality.
No institution needs to use PurePortal, of course. Any feature in either version of PurePortal can be made on an institution's own web pages by the institution's own internal or external web programmers. Data for such an exercise would then be retrieved from Pure's Web-Service API, and the desired functionality and rendering would be made by the local web programmers.
Please see the Web-Service section above or the more technically detailed section under TECH below.
The following resources are available with this page:
A demo report illustrating how data can be aggregated by individuals and organisational units, for example, and represented in a matrix, a table, in lists, and as various graphs.
136 screenshots from Pure 4.10.0 in english language. Images may be used in presentations and for educational purposes when naming atira.dk as the source.
Niels Jernes Vej 10
9220 Aalborg Oest
Phone: (+45) 96 35 61 00
VAT no. 26835526
Our technical area is server-side application architecture, development, and implementation. Our business domain is Research Information Management. We supply our product Pure, an enterprise-class CERIF-based CRIS system.
Pure, released in 2003, is licensed for 47,900 research staff at our 75 references in 8 countries.
Copyright © 2012 Atira A/S, a Reed Elsevier Company. All rights reserved.
Cookies page.Cookies are set by this site. To decline them or learn more, visit our