|Date||Elements concerned||Update information for the English version|
|19 June 2019||Launch of Papago at the University of Lausanne||Papago, the Open Access personal assistant has been deployed at the University of Lausanne (French version).|
|15 August 2019||Launch of Papago at the University of Lausanne||
Papago, the Open Access personal assistant has been deployed at the University of Lausanne (English version).
|30 August 2019||Multi-lingual support and institutional personnalisation||It is now possible to deploy Papago in four languages (FR, EN, DE, IT) and to personalise the sheets with other swiss higher education institutional identities and links. Visit our GitHub page to learn how to do it.|
|14 October 2019||Official full release of Papago||Official full release of Papago with SHERPA/RoMEO and disciplinary functionality.|
|7 April 2020||New SHERPA/RoMEO API||
Papago now uses the new SHERPA/RoMEO API.
|17 novembre 2020||Addition of Read & Publish agreements||
Papago can now recognise journals that are part of specific agreements with UNIL allowing our authors to publish in Open Access free of charge and indicates this in the "funding opportunities" section.
|1 May 2021||Addition of Wiley Read & Publish agreement||Papago now recognises journals that are part of the national Wiley Read & Publish agreement.|
|8 June 2021||Removal of Héloïse links||Héloïse is now off line. Links concerning it have been removed from Papago.|
|30 August 2022||Migration and update of Read & Publish licences||
Papago has been migrated to a more modern and powerful server. ACM, AIP and IOP have been added to the Read & Publish licenses recognised by Papago.
The adapted concept, logic tree and original answer sheets in French were developed by Micaela Crespo from the Department of Research and International Relations of the University of Lausanne. The source code for this tool was developed by Thomas Henkel of the Cantonal and University Library of Friboug. It can be reused, modified, built upon and improved freely, but we ask that the authorship of the code be attributed to the Papago project. The code is available to all on our GitHub page.
If you have any questions or comments about Papago, you can write to us at firstname.lastname@example.org. In addition, if you encounter an error or malfunction, do not hesitate to report it to us.
This project was strongly inspired by the tool on the Rights and Obligations of Researchers to Distribute their Publications in Open Access developed by the University of Lille, Willo.
We would like to thank Romain Féret of the Digital Library Department at the University of Lille for his collaboration, advice and support in the design of this tool.
This tool was developed as a collaboration between the Université de Lausanne and the Université de Fribourg. We wholehartedly thank our colleagues from the Swiss National Open Access Work Group and the Research Consultants at the University of Lausanne for their feedback during beta testing. We also thank Andrea Hacker (University of Bern) and Silvio Blindella (USI) for the English and Italian translations, respectively.
In view of the multilingual situation in Switzerland, as well as this project, and the conversational nature of the personal assistant, we have named the Papago tool, a word in Esperanto meaning "parrot".
Papago is an online questionnaire that provides respondents with customized scenarios.
Papago is composed of 2 complementary parts:
Papago also uses SHERPA/RoMEO (http://sherpa.ac.uk/romeo/index.php), an online resource that aggregates and analyses publisher open access policies from around the world and provides summaries of self-archiving permissions and conditions of rights given to authors on a journal-by-journal basis, to further personalise the answer sheets depending on the Journal and its required embargo period.
Papago seeks to bring together in one place all the essential information on the rights and obligations of researchers with regard to the open access distribution of their publications. Based on the answers provided by the respondents, it makes it possible to build a personalized scenario, adapted to the researcher's situation.
The flowchart can be broken down into 2 phases (these two phases are transparent to the respondent):