Duration: Aug 3 2023 → Aug 3 2023
Conference | 2023 Annual INL Intern Poster Session |
---|---|
Country/Territory | United States |
City | Idaho Falls |
Period | 08/3/23 → 08/3/23 |
Internet address |
T1 - Elsevier Pure Research Information Management System
AU - Milton, Emily
AU - Diaz, Eduardo
N2 - Pure is the research information management system (RIMS) from Elsevier, a company dedicated to helping researchers to advance science and better the future. This system has allowed Idaho National Laboratory (INL) to display their researchers, and the work done within the laboratory. The purpose of Pure is to allow researchers to network within INL but also with those outside INL. The methods we use involve analyzing resumes and curriculum vitaes (CV) and constant communication with researchers. The next steps of this project include outlining and creating a help page and instructional videos, for researchers to learn how to work pure themselves. Pure will impact networking inside and outside of INL, and it will highlight researchers inside INL and INL itself. In the poster we express the research outputs in pure, at this point of time. In addition, the poster expresses the trends from January 2023 until June 2023, for user activity and the types of research outputs.
AB - Pure is the research information management system (RIMS) from Elsevier, a company dedicated to helping researchers to advance science and better the future. This system has allowed Idaho National Laboratory (INL) to display their researchers, and the work done within the laboratory. The purpose of Pure is to allow researchers to network within INL but also with those outside INL. The methods we use involve analyzing resumes and curriculum vitaes (CV) and constant communication with researchers. The next steps of this project include outlining and creating a help page and instructional videos, for researchers to learn how to work pure themselves. Pure will impact networking inside and outside of INL, and it will highlight researchers inside INL and INL itself. In the poster we express the research outputs in pure, at this point of time. In addition, the poster expresses the trends from January 2023 until June 2023, for user activity and the types of research outputs.
M3 - Poster
T2 - 2023 Annual INL Intern Poster Session
Y2 - 3 August 2023 through 3 August 2023
How to use pure, the university's system for managing your research information..
See our film for using Pure
If you have any questions, please contact us.
On Monday 28 November 2022, applying for project funding will move to an online portal called Pure.
Accessed by the ‘Staff Applications’ page on the UNE Intranet, Pure will house all current awards and provide end to end funding applications.
This change affects all Researchers, Funding application reviewers, pre-approvers and approvers.
Familiarisation sessions are now being held. Please see the Pure Intranet page for session times and meeting links.
Important information regarding funding applications
For questions or more information, contact [email protected] .
© University of New England, 2024
The University of New England respects and acknowledges that its people, courses and facilities are built on land, and surrounded by a sense of belonging, both ancient and contemporary, of the world's oldest living culture. In doing so, UNE values and respects Indigenous knowledge systems as a vital part of the knowledge capital of Australia. We recognise the strength, resilience and capacity of the Aboriginal community and pay our respects to the Elders past, present and future.
PURE is a comprehensive research management system. It not only replaces the current research information system FIDES, but also integrates the full-text functions of ePubWU, and for the first time enables the digital management of the third-party funding process over the entire life cycle of projects.
A detailed manual is available in addition to training courses .
PURE distinguishes between the entry in the database and the external presentation of WU’s research output. Members of staff can access the database at research.wu.ac.at/admin and with their usual WU login (via single sign-on). You can reach the external presentation at research.wu.ac.at . This page is accessible to the general public and shows the research achievements of WU entered in PURE.
Unlike FIDES, which was an in-house developed solution, PURE is a commercial product provided by Elsevier. WU chose PURE as the best product for WU in a process guided by an external expert in research management. This change will enable us to further increase data quality, simplify the work steps for researchers and staff, and make WU's excellent research achievements even more visible to the outside world.
Information for Researchers
Our website uses cookies. Some of them are essential for the functionality of our website, while others are optional. By clicking the button “Accept all cookies,” you consent to all cookies, including cookies provided by US companies . This means that the personal data collected by the respective cookies are no longer subject to level of protection deemed appropriate under EU data protection law. In such cases, you only have very limited or no rights as a data subject in the US. In particular, the US government may gain access to these data. If you would like to reject all cookies or consent only to individual cookies, please click on “Individual settings” – this will allow you to manage your individual cookie preferences.
Name | Purpose | Lifetime | Provider |
---|---|---|---|
CookieConsent | Saves your consent to using cookies. | 30 days | WU |
site-popup | Saves if popup was filled or closed. | 30 days | WU |
BACH_PRXY_ID | To be able to display some WU-specific content, it is necessary that some information must be accessed by back-end WU systems. Required to assign the appropriate answer to a request. | 20 years | WU |
BACH_PRXY_SN | To be able to display some WU-specific content, it is necessary that some information must be accessed by back-end WU systems. Required to assign the appropriate answer to a request. | session | WU |
fe_typo_user | Required for login and access to protected content or for editing the user’s personal profile. | session | WU |
be_typo_user | Required for login and editing content in the TYPO3 back end. | session | WU |
be_lastLoginProvider | Stores the last method used for logging in to the TYPO3 back end. | 90 days | WU |
ASP.NET_SessionId | Required for assigning visitors to forms. | session | WU (forms.wu.ac.at) |
__RequestVerificationToken | Required to protect forms against attacks. | session | WU (forms.wu.ac.at) |
ESRASOFTSID | Required for identifying the logged-in user in the Business Language Center’s course registration system. | session | WU (esrasoft.wu.ac.at) |
esraSoftWiData | Required to track the language and language courses selected by the user. | session | WU (esrasoft.wu.ac.at) |
esraSimpleSAMLAuthToken | Required for identifying WU employees during the course registration process. | session | WU (esrasoft.wu.ac.at) |
esraSimpleSAML | Required for identifying WU employees during the course registration process. | session | WU (esrasoft.wu.ac.at) |
SimpleSAML | Required for identifying WU employees during the course registration process. | session | WU (esrasoft.wu.ac.at) |
Name | Purpose | Lifetime | Provider |
---|---|---|---|
_pk_id | Used by Matomo Analytics to store a few details about the user, such as the unique visitor ID. | 30 days | WU (piwik.wu.ac.at) |
_pk_ref | Used by Matomo Analytics to store the attribution information, the referrer initially used to visit the website. | 6 months | WU (piwik.wu.ac.at) |
_pk_ses | Created by Matomo Analytics, short-lived cookies used to temporarily store data for the current visit. | 1 hours | WU (piwik.wu.ac.at) |
_gcl_au | Contains a randomly generated user ID. | 3 months | |
AMP_TOKEN | Contains a token that can be used to retrieve a Client ID from AMP Client ID service. Other possible values indicate opt-out, request in progress or an error retrieving a Client ID from AMP Client ID service. | 1 year | |
_dc_gtm_--property-id-- | Used by DoubleClick (Google Tag Manager) to help identify the visitors by either age, gender or interests. | 2 years | |
_ga | Contains a randomly generated user ID. Using this ID, Google Analytics can recognize returning users on this website and merge the data from previous visits. | 2 year | |
_gat_gtag | Certain data is only sent to Google Analytics a maximum of once per minute. As long as it is set, certain data transfers are prevented. | 1 minute | |
_gid | Contains a randomly generated user ID. Using this ID, Google Analytics can recognize returning users on this website and merge the data from previous visits. | 24 hour | |
_gac_gb | Contains campaign-related information for the user. If Google Analytics and Google Ads accounts are linked, the conversion tags on the Google Ads website read this cookie. | 90 day | |
_dc_gtm | Used to throttle the request rate. | 1 minute | |
IDE | Contains a randomly generated user ID. Using this ID, Google can recognize the user across different websites across domains and display personalized advertising. | 1 year | |
player | This cookie saves user-specific settings before an embedded Vimeo video is played. This means that the next time you watch a Vimeo video, your preferred settings will be loaded. | 1 year | Vimeo |
vuid | This cookie is used to save the usage history of the user. | 2 year | Vimeo |
__cf_bm | This cookie is used to distinguish between humans and bots. This is necessary for Vimeo to collect valid data about the use of the service. | 1 day | Vimeo |
_uetvid | This cookie is set to enable the use of the Vimeo video player. | 1 year | Vimeo |
_tt_enable_cookie | This cookie is used to enable the vimeo video embedding on the WU Website and for other unspecified purposes. | 1 year | Vimeo |
afUserId | This cookie collects data from users who interact with embedded Vimeo videos. | 2 years | Vimeo |
_abexps | This cookie saves settings made by the user, e.g. Default language, region or username as well as interaction data of the user with Vimeo | 10 months | Vimeo |
_clck | This cookie enables the use of the embedded Vimeo video player | 1 year | Vimeo |
has_logged_in | This cookie stores login information and if the user has ever logged in. | 10 years | Vimeo |
language | This cookie remembers the language setting of a user. This ensures that Vimeo appears in the language selected by the user. | 11 years | Vimeo |
_ttp | This cookie is set to enable the use of the Vimeo video player | 1 year | Vimeo |
sd_client_id | This cookie stores data about the users current video settings and a personal identification token | 2 year | Vimeo |
_rdt_uuid | This cookie collects data about the users actions on websites that have a vimeo video embedded. | 3 months | Vimeo |
vimeo_cart | This cookie is used to check how many times a video has been played by the user. | 10 years | Vimeo |
OptanonConsent | This cookie stores information about the consent status of a visitor. | 1 year | Vimeo |
_scid | This cookie is used to assign a unique ID to a user | 10 months | Vimeo |
hjSessionBenutzer_ | Set when a user first lands on a page. Persists the Hotjar User ID which is unique to that site. Hotjar does not track users across different sites. Ensures data from subsequent visits to the same site are attributed to the same user ID. | 1 year | Hotjar |
_hjid | This is an old cookie which is not set anymore, but if a user has it unexpired in their browser. It will be reused and migrated to _hjSessionUser_{site_id}. Set when a user first lands on a page. Persists the Hotjar User ID which is unique to that site. Ensures data from subsequent visits to the same site are attributed to the same user ID. | 1 year | Hotjar |
_hjFirstSeen | Identifies a new users first session. Used by Recording filters to identify new user sessions. | 30 minutes | Hotjar |
_hjHasCachedUserAttributes | Enables us to know whether the data set in _hjUserAttributes Local Storage item is up to date or not. | session | Hotjar |
_hjUserAttributesHash | Enables us to know when any User Attribute has changed and needs to be updated. | 2 minutes | Hotjar |
_hjBenutzerAttribute | Stores User Attributes sent through the Hotjar Identify API. No explicit expiration. | session | Hotjar |
hjViewportId | Stores user viewport details such as size and dimensions. | session | Hotjar |
hjActiveViewportIds | Stores user active viewports IDs. Stores an expirationTimestamp that is used to validate active viewports on script initialization. | session | Hotjar |
_hjSession_ | Holds current session data. Ensures subsequent requests in the session window are attributed to the same session. | 30 minutes | Hotjar |
_hjSessionTooLarge | Causes Hotjar to stop collecting data if a session becomes too large. Determined automatically by a signal from the server if the session size exceeds the limit. | 1 hour | Hotjar |
_hjSessionResumed | Set when a session/recording is reconnected to Hotjar servers after a break in connection. | session | Hotjar |
_hjCookieTest | Checks to see if the Hotjar Tracking Code can use cookies. If it can, a value of 1 is set. Deleted almost immediately after it is created. | session | Hotjar |
_hjLocalStorageTest | Checks if the Hotjar Tracking Code can use Local Storage. If it can, a value of 1 is set. Data stored in _hjLocalStorageTest has no expiration time, but it is deleted almost immediately after it is created. | none | Hotjar |
_hjSessionStorageTest | Checks if the Hotjar Tracking Code can use Session Storage. If it can, a value of 1 is set. Data stored in _hjSessionStorageTest has no expiration time, but it is deleted almost immediately after it is created. | none | Hotjar |
_hjIncludedInPageviewSample | Set to determine if a user is included in the data sampling defined by your site's pageview limit. | 2 minutes | Hotjar |
_hjIncludedInSessionSample_ | Set to determine if a user is included in the data sampling defined by your site's daily session limit. | 2 minutes | Hotjar |
_hjAbsoluteSessionInProgress | Used to detect the first pageview session of a user. | 30 minutes | Hotjar |
_hjTLDTest | We try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. Enables us to try to determine the most generic cookie path to use, instead of page hostname. It means that cookies can be shared across subdomains (where applicable). After this check, the cookie is removed. | session | Hotjar |
Name | Purpose | Lifetime | Provider |
---|---|---|---|
test_cookie | Is set as a test to check whether the browser allows cookies to be set. Does not contain any identification features. | 15 minute | |
IDE | Contains a randomly generated user ID. Using this ID, Google can recognize the user across different websites across domains and display personalized advertising. | 1 year | |
_gcl_au | Contains a randomly generated user ID. | 90 day | |
_gcl_aw | This cookie is set when a user clicks on a Google ad on the website. It contains information about which ad was clicked. | 90 day | |
xs | Used to maintain a Facebook session. It works in combination with the c_user cookie to authenticate the user's identity on Facebook. | 1 year | |
fr | Used to serve advertisements and measure and improve their relevance. | 90 day | |
m_pixel_ratio | Performance cookie used by Facebook with Facebook pixels. | session | |
wd | Used for analysis purposes. Technical parameters are logged (e.g. aspect ratio and dimensions of the screen) so that Facebook apps can be displayed correctly. | 7 day | |
dpr | Used for analysis purposes. Technical parameters are logged (e.g. aspect ratio and dimensions of the screen) so that Facebook apps can be displayed correctly. | 7 day | |
sb | Used to save browser details and Facebook account security information. | 2 year | |
dbln | Used to save browser details and Facebook account security information. | 2 year | |
spin | Cookie for advertising purposes and reporting on social campaigns. | session | |
presence | Contains the "Chat" status of a logged in user. | 1 month | |
x-referer | Performance cookie that is used by Facebook in combination with Facebook pixels. | session | |
cppo | Cookie for statistical purposes. | 90 day | |
datr | Identifies the browser for security and website integrity purposes, including account recovery and identification of potentially compromised accounts. | 2 year | |
locale | Saves language settings. | session | |
_fbp | A cookie for Facebook advertising that is used to track and improve relevance and to serve ads on Facebook. | 90 day | |
_fbc | A cookie for Facebook advertising that is used to track and improve relevance and to serve ads on Facebook. | 90 day | |
UserMatchHistory | This cookie is used to synchronize the LinkedIn Ads IDs. | 30 day | |
AnalyticsSyncHistory | This cookie saves the time at which the user was synchronized with the "lms_analytics" cookie. | 30 day | |
li_oatml | This cookie is used to identify LinkedIn members outside of LinkedIn for advertising and analysis purposes. | 30 day | |
lms_ads | This cookie is used to identify LinkedIn members outside of LinkedIn. | 30 day | |
lms_analytics | This cookie is used to identify LinkedIn members for analysis purposes. | 30 day | |
li_fat_id | This cookie is an indirect member identification that is used for conversion tracking, retargeting and analysis. | 30 day | |
li_sugr | This cookie is used to determine probabilistic matches of the identity of a user. | 90 day | |
U | This cookie identifies the user’s browser. | 3 month | |
_guid | This cookie is used to identify a LinkedIn member for advertising via Google Ads. | 90 day | |
BizographicsOptOut | This cookie is used to determine the rejection status for tracking by third-party providers. | 10 year | |
lidc | This cookie makes it easier to select LinkedIn's data center. | 24 hours | |
aam_uuid | This cookie is used for ID synchronization with Adobe Audience Manager. | 30 days | |
AMCV_XXX_at_AdobeOrg | This cookie contains a unique identifier for the Adobe Experience Cloud. | 180 days | |
li_mc | This cookie is used as a temporary cache. It is used to have the user's consent information from the database available client side. | 2 years | |
lang | This cookie stores the language settings of a user. This ensures that the LinkedIn.com website appears in the language selected by the user. | session | |
twll | This cookie is set when X is embedded on the page. X collects data that is mainly used for tracking and targeting. | 4 year | X |
secure_session | This cookie is set when X is embedded on the page. E.g. X's like or sharing functions. | 14 year | X |
guest_id | This cookie is set by X when a visitor shares content from the WU website on X. | 2 year | X |
personalization_id | This cookie is set by X to measure the performance of X advertising campaigns in a user's browsers and devices | 2 year | X |
remember_checked | This cookie is set by when X is embedded on the page. X collects data that is mainly used for tracking and targeting. | 4 year | X |
remember_checked_on | This cookie is set when X is embedded on the page. E.g. X's like or sharing functions. | 4 year | X |
mbox | This cookie is intended for identifying X users, for analyzing interaction with the X Service and advertising whitin the service. | 2 years | X |
guest_id_ads | This cookie is set due to X integration and for sharing content to social media. | 10 months | X |
d_prefs | This cookie ist used to check referral links and the login status. | 90 days | X |
ct0 | This cookie is set due to X integration and sharing capabilities for the social media. | 10 months | X |
kdt | This cookie is used to monitor the users login status on X. | 10 months | X |
guest_id_marketing | This cookie is set for tracking and analytics purposes. | 10 months | X |
twid | This cookie checks if you are logged in to X during a browser session. | 1 year | X |
auth_token | This cookie is required for authentication and checks whether the user is logged in. | 10 months | X |
external_referer | This cookie collects statistical data, including how often you visit X and how long a user stays on X. | 1 day | X |
NID | This cookie contains a unique ID that is used to save user-specific settings and other information, in particular your preferred language, how many search results should be displayed per page and whether the Google SafeSearch filter should be activated. | 6 month | YouTube |
1P_JAR | This Google cookie is used to optimize advertising, to provide ads that are relevant to users, to improve reports on campaign performance or to prevent a user from seeing the same ads multiple times. | 1 month | YouTube |
CONSENT | This cookie is used to support Google's advertising services. | 20 year | YouTube |
OTZ | Aggregated analysis of website visitors. | 17 day | YouTube |
by Estelle Boshoff | Jul 14, 2022 | Uncategorized | 0 comments
The RIMS project team is getting ready to roll out the new Research Information Management System (RIMS), first announced in November 2021, across the university. The implementation will take a phased approach with the first phase to be implemented in Spring 2022.
The system is based on the Elsevier Pure product and will provide UNE with a versatile, centralised research information management system.
Following implementation of Phase 1, UNE will be able to manage awarded projects, build useful reports, carry out performance assessments, manage researcher profiles, enable research networking and expertise discovery, and reduce manual administrative burdens for researchers, faculties and staff.
Information will be stored centrally, significantly simplifying management of academic and administrative workloads by offering a single source of information and project management solutions such as milestone management, reporting and quality control, and providing a holistic view of UNE’s research portfolio. Previously, academics were unable to access their overall project information from Research Master – milestones were sought from the grants team, contract details from legal, invoicing timelines from finance resulting in inconsistent project management approaches across the university.
The new RIMS will also eliminate the multiple paper-based processes currently being used such as project approval forms and emailed approval trails, and allow the researchers to have ownership and control of their projects from conception to completion.
Update your profiles!
In anticipation of RIMS going live in September/October, academic staff are asked to ensure their are update.
The RIMS project has a team of consultants working to update the academic staff profiles in both the current “Find an Expert” search and the new, soon to be launched Research Information Management System. The aim is to support academics with updating their profiles so prospective HDR students searching for a supervisor, or anyone searching for an expert in a particular field for collaboration can easily access the information they need.
Academic staff members should have received an email from a RIMS consultant asking them to fill in a prepopulated spreadsheet that will allow the team to update their research profiles in both the existing staff profile (they will create it if one doesn’t exist) and the profile for the new RIMS.
The team’s intention is to make “Find an Expert” and the new RIMS as accurate and up to date as and they would appreciate it if everyone could jump on board and send their spreadsheets back as soon as possible.
If you’re unsure about the spreadsheet or didn’t receive a request to update your research profile, contact [email protected] .
Over the next couple of months, the RIMS project team will also commence testing and training of researchers, faculties and staff in preparation for implementation. You can follow their progress via our updates in PULSE.
Your email address will not be published. Required fields are marked *
Save my name, email, and website in this browser for the next time I comment.
S | M | T | W | T | F | S |
---|---|---|---|---|---|---|
2 | ||||||
3 | 4 | 5 | 8 | 9 | ||
10 | 11 | 12 | 13 | 15 | 16 | |
17 | 18 | 19 | 22 | 23 | ||
24 | 25 | 26 | 27 | 29 | 30 | |
31 |
Systems support for Pure, Worktribe, Research Professional and Equipment.data
This team looks after the system administration, training and reporting for the University's various Research Information Management systems, including Pure, Worktribe, Research Professional and Equipment.data.
Pure is the University's Current Research Information System (CRIS)
Worktribe Research Management provides Research Application and Award activity support
Research Professional is an online service offering access to a vast, up-to-date database of research funding opportunities
Equipment.data is the University's research equipment database
Pure is the University of St Andrews’ research information system which brings together key information on all aspects of research at St Andrews.
Pure captures a wide range of research-related outcomes, such as:
Pure content can also be shared with other research information and analysis systems such as ORCID , Researchfish and Altmetrics for Institutions .
This edition of Keeping Up With… was written by Marlee Givens.
Marlee Givens is Strategic Initiatives Manager at the Georgia Tech Library, email: [email protected] .
In a 2014 blog post , Lorcan Dempsey (OCLC Vice President, Membership and Research, Chief Strategist) wrote about Research Information Management Systems (RIMS) as a potential new service category for libraries. RIMS collect and store structured data about faculty research and scholarly activities for one institution, with the intention of repurposing the information in a variety of ways. Academic institutions in the U.S. and Canada are implementing systems such as Activity Insight, Pure, Converis, and Symplectic Elements, which track publications and scholarly activities of faculty. These systems give an overall picture of the research and scholarly enterprise of an institution, and they offer faculty tools for collaborating, publicizing their work, complying with policies (such as open access policies), and creating reports for faculty annual review or promotion and tenure.
It is important to note that RIMS is not the only name by which these systems are known. In Europe, where these systems were first developed and used, a more common term is Current Research Information Systems (CRIS). Other terms include “profile system” or “networking tool” and variations thereof.
Several RIMS platforms are available and offer varying options. Many tools have particular strengths in one aspect of research information management, such as publication and grants management, faculty activity reporting, or collaboration and networking for research and scholarship. A useful Wikipedia article compares systems and provides information on their data sources and formats, interoperability and integration, functionality, controlled vocabulary or ontologies, and bibliometrics.
These systems are distinguished from other web-based networking sites such as LinkedIn or Google Scholar in terms of their authority (RIMS ingest data from authoritative sources) and metrics tools (such as Journal Impact Factor or Altmetrics). They also employ standards or common data formats for interoperability, enabling importation of external data and reuse of system data, such as for CV’s and biosketches, or to populate the institutional repository.
Below are some of the more well-known RIMS in the U.S. and Canada. Many platforms offer more functionality than the descriptions below imply, and providers are regularly adding new features and modules. Some institutions choose to use one platform, while others use a combination of platforms for different purposes. Interoperability standards allow for multiple systems to communicate or export data to other systems.
Converis, Pure, and Symplectic Elements offer robust functionality for publication and grant award management, and they are increasingly being used for faculty activity reporting.
Digital Measures and Data180 offer platforms for faculty activity reporting and CV creation.
Profiles and VIVO are designed for research networking and collaboration, providing a web-based snapshot of faculty scholarship in an online profile and tools for finding expertise within research areas.
Standards for RIMS are evolving. The CRIS community in Europe uses a common standard, CERIF (Common European Research Information Format), to support exchange of data between RIMS. The Consortia Advancing Standards in Research Administration Information (CASRAI) has developed a dictionary of common terms used in research administration information. In addition, RIMS can provide metrics from providers like Thomson Reuters (Research Analytics) and Elsevier (Snowball Metrics), or emerging alternatives (such as Altmetric). RIMS can also use ORCID (Open Researcher and Contributor ID) identifiers for author disambiguation.
RIMS benefit academic institutions through both their efficiency and their effectiveness. Providing a central repository of information about faculty scholarship and research activities, from which multiple outputs may be exported, allows for efficient capture and reuse of faculty data. RIMS can help increase the visibility of scholarship on campus, show trends in funding or research areas, and identify expertise for grant applications, interdisciplinary research collaboration, or campus communications. By capturing data from authoritative sources and offering tools for analytics and metrics, RIMS also address a strategic need on many campuses to show the effectiveness of academic programs.
However, adopting RIMS can be a slow process. Outside of grants and publications, much of the information an institution may want to capture about their faculty does not have a source and requires manual entry (for example, honors and awards, students mentored, journal editorships, or society memberships). Non-federal grant data is difficult to capture automatically. In the area of publications, coverage for many disciplines (especially humanities and social sciences) or for particular publication types (especially grey literature such as lectures, technical reports, or white papers) is not complete in the available automated data sources. There may also be organizational or political roadblocks: resistance from faculty, a lack of resources for data entry, or funding issues.
Libraries implement these systems in a number of ways, from tracking publications, to creating links to institutional repositories, to leadership, training and funding. In some cases, the library’s work with RIMS is an extension of the scholarly output assessment services already provided. For example, the library may already be involved in research data management, operating a repository, or supporting institutional review and accreditation. Library involvement in RIMS implementation is a natural extension of all of these roles, and offers an opportunity for the library to advocate for positive changes in scholarly communication, such as open access or alternative measures of research impact. However, the library may also easily fall into a purely administrative role with RIMS implementation. The earlier the library can establish a place at the table, the better the chance it has in adopting a leadership and advocacy role.
Börner, Katy, Michael Conlon, Jon Corson-Rikert, and Ying Ding. 2012. VIVO: A semantic approach to scholarly networking and discovery . Morgan & Claypool Publishers. http://www.morganclaypool.com/doi/abs/10.2200/S00428ED1V01Y201207WBE002 .
Bryant, Rebecca, Ruth Allee, Kate McCready, and Julie Speer. 2015. "Facilitating researcher discovery across all disciplines : challenges and strategies for implementing campus researcher profiles for humanists and social scientists." Digital Library Federation (DLF), October 26. http://hdl.handle.net/2429/55689 .
Chin Roemer, Robin, and Rachel Borchardt. 2014. "Keeping up with... Altmetrics." Accessed February 29, 2016. http://www.ala.org/acrl/publications/keeping_up_with/altmetrics .
Dempsey, Lorcan. 2014. "Research information management systems – a new service category?" Lorcan Dempsey's Weblog . October 26. Accessed February 29, 2016. http://orweblog.oclc.org/research-information-management-systems-a-new-service-category/ .
Jacobs, Neil. 2015. "Research information management." In Digital Information Strategies: From Applications and Content to Libraries and People , by David Baker and Wendy Evans, 57-69. Chandos Publishing.
Kennan, Mary Anne, Sheila Corrall, and Waseem Afzal. 2014. "“Making space” in practice and education: research support services in academic libraries." Library Management 35 (8/9): 666-683. Accessed March 2, 2016. doi:http://dx.doi.org/10.1108/LM-03-2014-0037 .
MacColl, John, and Michael Jubb. 2011. "Supporting Research: Environments, Administration and Libraries." OCLC Research . Accessed March 2, 2016. http://www.oclc.org/content/dam/research/publications/library/2011/2011-10.pdf .
Ribeiro, Ligia, Pablo de Castro, and Michele Mennielli. 2016. "Final report: EUNIS – EUROCRIS joint survey on CRIS and IR." euroCRIS . Accessed March 7, 2016. http://www.eurocris.org/sites/default/files/files/cris-report-ED(1).pdf .
Russell, Rosemary. 2012. "Adoption of CERIF in Higher Education Institutions in the UK: A Landscape Study." UKOLN . March 22. Accessed March 2, 2016. http://opus.bath.ac.uk/30979/3/CERIF_UK_landscape_report_v1.1.pdf .
Wikipedia. n.d. "Comparison of research networking tools and research profiling systems." Wikipedia . Accessed February 29, 2016. https://en.wikipedia.org/wiki/Comparison_of_research_networking_tools_and_research_profiling_systems .
Share This Page
Discover the world's research
To read the full-text of this research, you can request a copy directly from the authors.
Rmi based distributed research information management and usage: in case of debre markos university burie campus, data blind: universities lag in capturing and exploiting data, creating structured linked data to generate scholarly profiles: a pilot project using wikidata and scholia, futuristic invisibility for user identity and data protection.
Research data meets research information management: two case studies using (a) pure cerif-cris and (b) eprints repository platform with cerif extensions, making research data repositories visible: the re3data.org registry, researchers’ participation in and motivations for engaging with research information management systems, institutional repositories and research data curation in a distributed environment, implementation of a research information management system in a pediatric hospital, kultivating kultur: increasing arts research deposit, research data repositories: review of current features, gap analysis, and recommendations for minimum requirements, from invisibility to impact: recognising the scientific and societal relevance of interdisciplinary sustainability research, research information management: making sense of it all, related papers.
Showing 1 through 3 of 0 Related Papers
IMAGES
VIDEO
COMMENTS
Pure is a Research Information Management System (RIMS) or Current Research Information System (CRIS) designed to be simple and turnkey. Deep integration into the Research Intelligence portfolio and external Open Access (OA) databases and Open Data repositories enables actionable analysis across sources for enhanced decision-making and evidence-based execution of research strategy.
Pure brings together research information from multiple disparate sources on one easy-to-use platform, creating a bird's eye view of all your activities. ... Research Information Management System (RIMS)—also known as a Current Research Information System (CRIS)—is a technology-based information solution that integrates and links various ...
It has been interesting watching Research Information Management or RIM emerge as a new service category in the last couple of years. Oct 26, 2014 9 min read. RIM is supported by a particular system category, the Research Information Management System (RIMs), sometimes referred to by an earlier name, the CRIS (Current Research Information System).
Pure captures a wide range of data about our University's research, and serves as a single point of access for research management information. ... Pure is a Current Research Information System (CRIS), collecting a range of information about University's research. This is used for internal and external reporting, performance review ...
Over 6,000 are using Research Intelligence solutions for data and information to tackle issues their researchers are facing. University of Surrey uses SciVal to increase collaboration. UTMB leveraged Pure to promote and report on its COVID-19 response. Herzen University uses Scopus to develop enhanced reporting and decision-making tools.
Pure is the research information management system (RIMS) from Elsevier, a company dedicated to helping researchers to advance science and better the future. This system has allowed Idaho National Laboratory (INL) to display their researchers, and the work done within the laboratory.
Pure user guides. How to use Pure, the University's system for managing your research information. Pure gives an insight into University's research collaborations.
Pure is the University's Current Research Information System ( CRIS ). Information held in Pure relates to research staff and their publications, projects and activities information. Pure allows for relationships and associations to be created between research inputs and outputs, providing a broad picture of research activity at the individual ...
Introducing Pure; UNE's new Research Information Management System. Published 23 November 2022. On Monday 28 November 2022, applying for project funding will move to an online portal called Pure. Accessed by the 'Staff Applications' page on the UNE Intranet, Pure will house all current awards and provide end to end funding applications.
PURE is a comprehensive research management system. It not only replaces the current research information system FIDES, but also integrates the full-text functions of ePubWU, and for the first time enables the digital management of the third-party funding process over the entire life cycle of projects. A detailed manual is available in addition ...
The system is based on the Elsevier Pure product and will provide UNE with a versatile, centralised research information management system. Following implementation of Phase 1, UNE will be able to manage awarded projects, build useful reports, carry out performance assessments, manage researcher profiles, enable research networking and ...
a Research Information Management System (also known as a Current Research Information System, or CRIS) in supporting the REF submissions process. It provides an overview of the bespoke modules and functionalities within Symplectic Elements which have been designed to empower HEIs in gathering and collating information
Systems support for Pure, Worktribe, Research Professional and Equipment.data. This team looks after the system administration, training and reporting for the University's various Research Information Management systems, including Pure, Worktribe, Research Professional and Equipment.data.
For REF and general PURE related queries contact: Claire Davis, Research Assessment Manager, For output and dataset related queries contact: Michelle Walker, Repository and Research Data Manager, For Impact related queries contact: Impact and RCUK Officer, REO For technical help with the PURE system contact: University IT Helpdesk.
Pure is the University of St Andrews' research information system which brings together key information on all aspects of research at St Andrews. Pure captures a wide range of research-related outcomes, such as: publications; datasets; impacts; Open Access compliance; professional activities. Pure content can also be shared with other ...
In a 2014 blog post, Lorcan Dempsey (OCLC Vice President, Membership and Research, Chief Strategist) wrote about Research Information Management Systems (RIMS) as a potential new service category for libraries. RIMS collect and store structured data about faculty research and scholarly activities for one institution, with the intention of ...
Abstract. Research information management systems (RIMS) are the emerging new service in academic and research libraries. RIMS support universities and libraries in managing their institute ...
the research and results. Research Information Management Systems are commonly referred to by a few names and acronyms, including RIMS, Current Research Information Systems or CRIS. These systems increase the eiciency and efectiveness of research information management activities by integrating and linking the various
This chapter provides a comparative evaluation of RIMS (i.e., PURE-Elsevier, Converis-Thomson Routers, and Symplectic Elements) and assists with the selection of the appropriate software application for implementation of a RIMs system in universities and libraries. Research information management systems (RIMS) are the emerging new service in academic and research libraries. RIMS support ...