"C" Develop Demonstrators
The third objective is "To use demonstrators implementing pilot repository infrastructure in research universities to explore the leadership roles that regional universities can take in larger collaborative arrangements".
RUBRIC activities for this objective will include:
C1 Participating in user and advisory groups where possible
C2 Negotiating citation data availability with vendors (in partnership with the University of Newcastle)
C3 Loading citation data to demonstrator
C4 Exploring repository citation data integration with open linking solutions
C5 Applying best practice from ARROW, ROMEO, SHERPA and MAMS to manage access and licensing issues for open linking to externally housed resources
C6 Mentoring repository project manager positions in partner universities to develop local expertise
C7 Loading citation data to partner universities and IRUA members
C8 Integrating RUBRIC with national and international discovery services
C9 Integrating RUBRIC repositories containing thesis data to ADT
C1: Members of the RUBRIC Project team hope to engage with formal groups wherever possible, through membership of advisory and technical groups, user groups and other suitable forums including contributing to relevant discussion lists and using newer media such as folksonomies and tagging to identify useful knowledge resources available online.
C2: Attempt to engage vendors in discussion about the purchase and availability of citation data that could be used to fast track the population of an institutional repository.
C3: There will be significant effort expended in testing batch ingest and export of data between various repository solutions by the central RUBRIC Technical Team. This will also tie in with exploration of data quality issues and reporting.
C4: It is hoped that there may be opportunities to explore emerging technologies such as open linking to provide links between the citation data and full text content available in databases subscribed to by the participating university.
C5: It will be necessary to explore a range of issues associated with the proposal to use open linking technologies to link citation data with full text content. This will involve debate about managed content vs open access content, accessibility issues, user expectations, "handles" and DOI management, data management issues such as ISSNs (where online versions may differ to print versions) and so on. A broader range of issues are expected to emerge during the life of the project.
C6: Once Project Manager positions are established at the RUBRIC partner organizations there will be a significant amount of mentoring provided by the central RUBRIC team. Most of this mentoring facility will be managed by the Business and Communications Coordinator based at USQ.
C7: This will be dependent on successful outcomes at other stages of the project. Providing it is possible to obtain high quality data from vendors or other sources which can be loaded using a batch ingest process, the RUBRIC Technical Team will continue to work with the data to ensure that it can be loaded to partner implementations as well as the centralized demonstrator systems.
C8: It is imperative that the data loaded into RUBRIC repositories is harvestable to national and international discovery services. The key services in mind are Google, Google Scholar, ADT and the ARROW discovery service. OAI compliance will be thoroughly tested and implemented at each partner site at the time of deployment.
C9: Until recently, many organizations have been running separate repositories to manage their thesis data as distinct from other data sources such as ePrints and grey literature (student theses, reports, conference papers etc). RUBRIC wishes to explore the co-location of ADT thesis data with other forms of data and utilize technologies such as METS packages to harvest sub-sets of data for reporting via various discovery services. This objective will be dependent on functionality being available in the software solutions implemented by the RUBRIC project.
