Report Open Access

Automation Tools for Invenio

Panagiotidou, Foteini


Dublin Core Export

<?xml version='1.0' encoding='utf-8'?>
<oai_dc:dc xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
  <dc:contributor>Ioannidis, Alexandros</dc:contributor>
  <dc:creator>Panagiotidou, Foteini</dc:creator>
  <dc:date>2020-04-06</dc:date>
  <dc:description>Invenio is an open source framework, initially developed at CERN, but with many external users
and contributors at this moment and prospects of growing even more in the future. Its nature as a digital
library for large scale repositories renders it a very useful tool in other software projects, inside and out of
CERN alike.

The maintenance of Invenio's software falls under the responsibility of the IT-CDA-DR section. The
big workload that the section has to manage combined with the currently inefficient work management
when it comes to Invenio, results in Invenio falling behind, which affects badly not only the section, which
makes great use of Invenio in various other projects, but also the Invenio community, which stays inactive.

The goal of my two month internship at CERN was to fix this problem by developing a bot that
would send reports to the maintainers of Invenio, concerning the Invenio related tasks they have to fulfil,
thus helping them to organize their work and do it more efficiently.

The bot was developed using the python programming language and various contemporary
technologies, such as git, github and gitter APIs, pytest, travis CI, docker and sphinx.

There currently exist two commands for the bot, "autobot report show", that shows the global report
for all maintainers and "autobot report send", that sends the personalised reports to each corresponding
maintainer.

The end result was a basic prototype for the bot and a lot of work remains to be done in the future. Some ideas for the future work are:


	Adjust the features to the users’ needs and desires.
	Improve the implementation resource-wise (e.g. cache the reports).
	Include customization features (e.g. sorting and filtering of the reports).
	Add synchronization with GitHub.
</dc:description>
  <dc:identifier>https://zenodo.org/record/3741752</dc:identifier>
  <dc:identifier>10.5281/zenodo.3741752</dc:identifier>
  <dc:identifier>oai:zenodo.org:3741752</dc:identifier>
  <dc:language>eng</dc:language>
  <dc:relation>doi:10.5281/zenodo.3741751</dc:relation>
  <dc:relation>url:https://zenodo.org/communities/cernopenlab</dc:relation>
  <dc:rights>info:eu-repo/semantics/openAccess</dc:rights>
  <dc:rights>https://creativecommons.org/licenses/by/4.0/legalcode</dc:rights>
  <dc:subject>CERN openlab</dc:subject>
  <dc:subject>summer student programme</dc:subject>
  <dc:title>Automation Tools for Invenio</dc:title>
  <dc:type>info:eu-repo/semantics/report</dc:type>
  <dc:type>publication-report</dc:type>
</oai_dc:dc>
88
62
views
downloads
All versions This version
Views 8888
Downloads 6262
Data volume 81.9 MB81.9 MB
Unique views 8282
Unique downloads 6161

Share

Cite as