Your SlideShare is downloading. ×
16.00 qs6 mon jo lambert
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

16.00 qs6 mon jo lambert

251
views

Published on

Published in: Technology, Education

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
251
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Go to ‘View’ menu > ‘Header and Footer…’ to edit the footers on this slide (click ‘Apply’ to change only the currently selected slide, or ‘Apply to All’ to change the footers on all slides).
  • The use cases illustrate the key problems that this Jisc Monitor seeks to address
  • Effective stakeholder engagement is considered crucial to support project development. The primary stakeholder is the academic institution. Other key stakeholders include publishers, funders, system vendors and other third parties such as subscription agents. A user-centredapproach to project development provides an opportunity to secure stakeholder buy-in and engagement and test ideas and developments. The project objective could be achieved through creation of a number of proof of concept demonstrators, evaluated in consultation with stakeholders in order to assess Jisc’s ability to support institutions in meeting requirements. A user-centred design process puts the institutional users at the heart of development. This achieves buy-in, support for the development and makes sure that the service is fit for purpose.The adoption of an agile approach to development provides a useful framework for the project. This enables the project teams to respond to opportunities as they arise and address the general challenges that exist within the sector.Outputs will be developed and released as Open Source software with supporting documentation being openly available.
  • The use cases illustrate the key problems that this Jisc Monitor seeks to address
  • Institutions require assistance in knowing whether their publications are compliant with the funder mandates. Currently this is difficult because:Institutions don’t always know the full extent of what they have publishedIt is not always easy for them to determine what OA options that the researcher chose in the publishers’ systems. If the information can be captured from the point of manuscript submission then there is less change of non-compliancePublishers often find it difficult to affiliate researchers to institutions and funders in their systems so Jisc Monitor interoperability module is keyInstitutions require some clarity around some of the funder’s OA requirements (e.g. RCUK) especially when it comes to reporting – they are looking at Jisc to help them in this area
  • The use cases illustrate the key problems that this Jisc Monitor seeks to address
  • Institutions require assistance on gathering intelligence on their publication activity. Currently this is difficult for them to do this on their own in practice as part of the scholarly communications takes place direct between the author and the publisher. Therefore they cannot always be confident that their systems have captured all of their publication activity. Institutions also want to know their total publication output whether it is Open Access or not. Furthermore if institutions are not aware of all of their publication output then they will not be fully aware of their degree of compliance with funder mandates.
  • Due to the different routes by which an institution may be paying their publication charges, it is often difficult for them to track the payments, especially for OA publications where an article may not be published until the publisher has received the payment. This is especially problematic if the fees are being paid via an intermediary and has in cases led to the authors being chased for payments that have already been made which can hold up the publication process. Institutions also require assistance for Jisc in terms of VAT reporting.Interoperability with institution finance systems has also been requested.If the financial data is being collected in Jisc Monitor then it would also make sense to link this with the subscription data via the Jisc Collections website to feed into the Total Cost of Ownership project. HEFCE is also interested in finding out in knowing the overall cost to institutions for OA publications and where they are receiving discounted publication charges
  • The use cases illustrate the key problems that this Jisc Monitor seeks to address
  • As the scholarly communications takes place direct between the authors and the publishers, this presents a number of problems:Institutions – the library and research office staff are not involved in the process and are therefore not always in the position to advise their researchers on what steps they need to take to ensure that they comply with funder mandates and institution policiesResearchers – the authors are not always sure what options they are supposed to take when using publisher systems to ensure that they select the correct licence when publishing their work. Any issues around non-compliance are then only likely to manifest themselves after the event.Publishers – they often have difficulty validating and associating a researcher to an institution e.g. how do I know that this researcher is actually from that university? The only people who can do that of course are the institution staff, hence the need to connect publisher and institution systems via Jisc Monitor.At the moment the same information is being entered several times into multiple systems. By developing the API’s that allows Jisc Monitor to interact with the different systems, this will save users time as the data will only need to be entered once in the relevant system as the data will be exchanged to the appropriate areas. This also allows the metadata to be enhanced by different users in the process as necessary.Jisc monitor will be interacting with a variety of systems such as IR’s / CRIS, subject repositories, funder systems as well as publisher systems
  • Transcript

    • 1. Jo Lambert and Brian Mitchell, Jisc Collections Jisc APC and Jisc Monitor: a shared approach UKSG, Harrogate, April 2014
    • 2. 14/04/14 UKSG 2014 2 Session aims » JiscAPC › introduction and aims › reflections on the pilot » Jisc Monitor › Aims › Use cases » Questions and comments
    • 3. 3 Jisc APC Pilot: aims & objectives APCs Systems and processes Information sharing Role of 3rd party provider APC administration platform
    • 4. 14/04/14 UKSG 2014 4 Managing APCS: reflections » Compliance and reporting requirements » Workflows and processes still being established » Managing communications » Infrastructures not yet in place » Standards - lack of/not fully adopted
    • 5. 14/04/14 UKSG 2014 5 Jisc APC platform: reflections » Level of APCs » Publisher engagement » Financial transactions » Data flow and exchange with other key systems » Value of an intermediary service
    • 6. 14/04/14 UKSG 2014 6 Jisc APC pilot outputs » Due by August 2014 » Case studies and analysis » Best practice guidelines » Data onAPCs » Pilot evaluation and report
    • 7. 14/04/14 UKSG 2014 7 Jisc Monitor context » Reflecting and building on outputs of Jisc APC » HEFCE policy will mandate open access availability for outputs accepted for publication after 1 April 2016 and submitted to the post -2014 REF » 1 year project starting May 2014 to scope and explore how a Jisc managed shared service might support institutions in meeting this requirement
    • 8. 14/04/14 UKSG 2014 8 Jisc Monitor outputs › Prototypes mapped to 4 use cases and released as free and open source software by April 2015 › Supported by robust user feedback and an assessment of the opportunities, challenges and dependencies that are likely to impact development › Recommendations for further development of components
    • 9. 14/04/14 UKSG 2014 9 Jisc Monitor pilot development » Managed by Jisc Collections and developed by Mimas utlising skills and expertise of Sero Consulting, Cottage Labs and Knowledge Integration › Articulation Strand – Iterative documentation and dissemination, including requirements, standards and interfaces, underpinning technical considerations › Exemplification Strand – Development of working prototypes for each of the four Use Cases; using iterative and agile development to work closely with users, systems / services and data › Implementation Strand (final quarter) Integration of prototypes where applicable, assessment of service options and future planning » Prototypes (funder compliance and publication activity available from September 2014, systems interoperability and publication charges due later )
    • 10. 14/04/14 10 Jisc Monitor use cases Monitoring all publication activity to ensure compliance with funder mandates Monitoring all publication activity to ensure a clear understanding of what has been published Standards development to enable efficient data exchange Monitoring spend on all items Jisc Monitor use cases
    • 11. 11 Jisc Monitor principles » Collaboration is key » User-centred development » Agile approach » Open-source
    • 12. 12 Jisc Monitor use cases Monitoring all publication activity to ensure compliance with funder mandates Monitoring all publication activity to ensure a clear understanding of what has been published Standards development to enable efficient data exchange Monitoring spend on all items Jisc Monitor use cases
    • 13. 14/04/14 UKSG 2014 13 Compliance with funder mandates » Jisc Monitor analyses publication data to determine whether it is compliant with funders’ mandates › Understanding full extent of what has been published › Checking OA options that a researcher chooses in the publishers’ system › Institutions require clarity around funder OA requirements
    • 14. 14 Jisc Monitor use cases Monitoring all publication activity to ensure compliance with funder mandates Monitoring all publication activity to ensure a clear understanding of what has been published Standards development to enable efficient data exchange Monitoring spend on all items Jisc Monitor use cases
    • 15. 14/04/14 UKSG 2014 15 Understanding what has been published » Jisc Monitor aggregates data from various sources in the form of a database / knowledge base of an institution’s publication activity › Capturing information about all publication activity › Need to be aware of all publication output to monitor degree of compliance with funder mandates
    • 16. 16 Jisc Monitor use cases Monitoring all publication activity to ensure compliance with funder mandates Monitoring all publication activity to ensure a clear understanding of what has been published Standards development to enable efficient data exchange Monitoring spend on all items Jisc Monitor use cases
    • 17. 14/04/14 UKSG 2014 17 Monitoring spend » Jisc Monitor provides data on how much an institution has spent on their OA publications and subscriptions › Difficulties of tracking payments › Assistance withVAT reporting › Interoperability with finance systems
    • 18. 18 Jisc Monitor use cases Monitoring all publication activity to ensure compliance with funder mandates Monitoring all publication activity to ensure a clear understanding of what has been published Standards development to enable efficient data exchange Monitoring spend on all items Jisc Monitor use cases
    • 19. 14/04/14 UKSG 2014 19 Standards and interoperability » Jisc Monitor connects publisher and institution systems to collate publication data from the point of manuscript submission to acceptance of manuscript and subsequent publication
    • 20. 14/04/14 UKSG 2014 20 Questions and comments › Questions? › General comments or reflections › Key issues or pain points within your organisation › Participate