The toolbar on this page offers options
that are relevant for the feature, such as Save.
Other options that are standard for other RME pages, such as New,
Next and Previous
are not relevant and are not displayed.
In this topic Hide
The RME Research Output Feeder Service is designed to import data for publications and other outputs from research from external source systems into RME. You can import publications data such as books, journal articles or conference proceedings from various sources, such as Scopus, ePrint and so on. It is normally scheduled to run as a Windows scheduled task using the RME Feeder Service Utility.
The feeder is designed to create new records when a match to an existing record cannot be found; it does not update existing records.
Unlike other RME feeders, this feeder is configured differently. This configuration page allows you to define the root network folder for all your source files, create an eForm from a record, and create profiles to manage the import and mapping of data.
Full details are available in the RME Research Outputs Feeder Guide, which is provided in the RME build package when you have the product key.
The toolbar on this page offers options
that are relevant for the feature, such as Save.
Other options that are standard for other RME pages, such as New,
Next and Previous
are not relevant and are not displayed.
Menu path: RME > Integrations > Research Outputs Feeder Service
The Research Output Feeder Service process involves the following key stages:
1. First, you create a research output profile for each source in the RME Research Output Profile page.
• In profile configuration, specify the data categories you want to use for mapping by uploading a CSV or tab delimited file.
• Enter source categories used in the source data, then map them to RME categories.
• Map fields from your source data to RME fields.
2. For each profile, create a matching folder with exactly the same name as the profile in the source file location.
3. Put files from the relevant source in this network folder. Name source files with the prefix: 'PUB_Publication'. For example, PUB_Publication_20170719.csv.
4. The RME Research Output Feeder is scheduled as a Windows service. When run, the feeder will go to the source file location, look in each profile folder and process any unprocessed files there.
5. The feeder looks for matches to existing data in RME based on certain criteria. If it cannot match an existing record, it will create a new record and feed data into the RME Database as mapped. For details, see: Research Outputs Feeder technical notes.
The feeder
only creates new records for unmatched entries. It does not update existing
records. It only sends data one way; it does not send data back to the
source system.
6. The feeder moves the processed source files into a “Processed” folder within the original profile folder.
The
toolbar on this page offers options that are relevant for the feeder,
such as Save. Other options that are standard for
RME pages, such as New, Next and Previous are not relevant for feeders and do not
display.
The sections below provide information to help you complete the fields in this page. For full details about the feeder service, refer to the RME Research Outputs Feeder Guide (PDF) provided separately in the RME build package.
Specify where in your network all the source files for the RME Research Outputs Feeder are or will be located.
When setting up the location, it is important to grant necessary read and write access permissions to the user under whose account the RME Research Outputs Feeder Windows scheduled task will run.
The program that generates the Research Outputs source data file must be able to access the network location with write access. All CSV files in the root network location will be considered as files for processing and will be processed at the next scheduled time.
For each source of research output data, such as Scopus or ePrint, you need to create a sub-folder under file path you specify in this field. The sub-folder name must also match the profile you set up for this source. All source extract file names must start with 'PUB_Publication'. Place the files to be processed under the sub-folder that corresponds to the source and profile name.
As you set up your own folders, there
is no defined template as used for other Finance, HR or Student feeders.
This function allows you to create an RME eForm based on each imported Research Output record imported. Slide the Create Online Form? option to Yes, then select the eForm template to use for the forms from the dropdown. eForms will be listed and available for selection in the RME Research Outputs domain.
Source: The eForm templates dropdown shows all the templates that are current and
published.
When you upload your profile file in step 1 above, field-level details can be viewed from the System > Documentation > Feeder Service page (under Research Outputs Feeder, or your customised name for this service, such as Publications Feeder).
This grid is a log of results from import activity. It indicates if importing was successful or if there were any exceptions or errors with a message. For example, if the system cannot find the defined network file or access the location, the message is "Failed : Source file path "xxx" cannot be found". In this case, you need to make sure that the network file is available and the root folder meets the requirements above in Source File Location.
If some items failed to import, a number displays in the Failed column. In this case, you can view a more detailed log by clicking the line entry to display the Research Output Feeder Import Results page.
To manage Research Output Profile records: You can also Add, Delete or Export using the links to the right of the grid.
Product Key: Feeder - Research Outputs
Page ID: FDR014.htm