LANTERN
SHINING A LIGHT ON OPEN ACCESS
Richard Jones, Founder, Cottage Labs
richard@cottagelabs.com
SHINING A LIGHT ON OPEN ACCESS
Richard Jones, Founder, Cottage Labs
richard@cottagelabs.com
It's a quick way to pull together metadata essential to calculating a work's compliance with an Open Access policy.
1. Effort reduction
Lantern can process a few thousand identifiers in a few hours. How much time to do manually?
2. Consistency and accuracy.
Results are easy to check, review and report on.
Increasingly there are OA mandates and policies appearing
And alongside those policies, there is the need for librarians/research offices/funders to report on and enforce them.
An OA policy that can't be enforced isn't of any value
Identifiers can consist of:
We'll take those as a spreadsheet, or if you're keen you can integrate with the API!
DOI | PMID | PMCID |
10.abc/123 | 78543277 | |
10.jkl/8999/1 | ||
78024443 | PMC75220165 | |
... | ... | ... |
Even though it's quick, Lantern still takes a bit of time.
It's going to go out to a range of places on the web to gather your compliance information. Right now thats:
When it's done, it'll email you
You can download your results as a spreadsheet, and it'll contain the following things:
Well, maybe "enforce" is too strong a word for higher education.
But you'll be able to review the results with the help of detailed provenance information Lantern provides, and determine how well your mandate compliance is going, and whether you need to have a quiet word with a couple of departments.
What's the correct community-focussed business model for services to Open Access?
There are a lot of possible answers to this question. We considered many, including: Feature-based Freemium, Usage-based Freemium, Public Good/Free, One cost for all, Tiered costs, Sponsorship, Membership and Grant Funded.
Usage-based Freemium
Secures access to the service for everyone in the community, and additional scale at cost for anyone that needs it, with a clean and clear business model.
You may remember the Open Article Gauge (it no longer exists). It was developed by Cottage Labs with funding from PLOS to page-scrape licence information from publisher websites
It used a long list of known licence statements. Those statements could be contributed by the community, but it was difficult to do, and the pool of contributors was small.
Instead, right now in Lantern we're managing this dataset internally.
Can we find a better way for the community to give us feedback, or new data? What is that mechanism? (seriously, we don't know yet).
Licence Type | Matches on Domains | Match Text |
cc-by | * | This is an open access article under the terms of the Creative Commons Attribution License, which permits use, distribution and reproduction in any medium, provided the original work is properly cited |
cc-by-nc | * | Creative Commons Non-Commercial |
cc0 | * | This is an open-access article, free of all copyright, and may be freely reproduced, distributed, transmitted, modified, built upon, or otherwise used by anyone for any lawful purpose. The work is made available under the Creative Commons CC0 public domain dedication. |
eudatagrid | * | EU DataGrid Software License |
There are some key areas where compliance data is hard to gather.
Can we help bring together a community effort to improve this metadata?
We've got a few big things on the list, but we're always looking for more:
If you have any, email us, or look at our public issue tracker
We want to be able to calculate whether a work is compliant with a given policy for you, but how do we work this out?
Is ROARMAP the right place to source the data from?
Pasteur4OA did some work on categorising policies - perhaps this is the place to start?
1. Scaling up for full service
We've officially launched and we're working with some early-adopters who are helping us make the service better.
2. Discussing a collaboration with Jisc to integrate with Monitor
Jisc's new OA and APC management tools will incorporate integration with Lantern as an option for all users, and we are discussing with Jisc a collaboration to bring Lantern to UK HEIs as part of their services to OA.
3. Building more features
as fast as we can, and based on your feedback
Richard Jones, Founder, Cottage Labs
richard@cottagelabs.com
twitter: @cottagelabs
email: lantern@cottagelabs.com
© Cottage Labs LLP 2011 - 2017. All site content CC-BY
Cottage Labs LLP is a software development consultancy partnership registered in Scotland with the number SO303454
Our VAT Registration number is 127710036
Our DUNS number is 21-736-0418