Inici de les pàgines wiki¶

Muscat a la UAB¶

• Tasques pendents després de la sortida a producció

Documentació per a la instal·lació i configuració inicial

• Muscat UAB installation notes: Només la primera vegada
• MariaDB databases configuration
• Solr installation notes

Documentació per a cada actualització

• Muscat UAB upgrading notes: Documentació rellevant per a instal·lar cada actualtizació
• Muscat UAB to production: Com passar un Muscat que tenim en proves a producció

Migració del DDD - 2023¶

• Gestió d'usuaris interns
• Registres d'autoritats
• Etiquetes Marc
• Historia
• Comentaris_grups_enfocats

Estudi previ al canvi de sistema¶

This working place aims to help us, current Invenio 1.x installations, to choose to follow Invenio 3 path or another software. Please feel free to contribute with your ideas.

We propose this structure, that we may change if it doesn't work well.

1. One wiki page for listing the current funcionality of our systems; or one wiki page per site, or per institution, I'm not sure yet.
2. One wiki page for listing the requirements for the next systems, from most important to less (maybe in groups?)
3. One wiki page for each alternative, at least with a line or two to know that we have taken a look and discarted it.

Overview¶

On March 19-21, 2019, there was an Invenio workshop at CERN about Invenio 3. There we saw how CERN envisions Invenio 3, and probably it is time for us to think if Invenio 3 fits our needs or not.

The following presentation, in English and the original Catalan, explains it:

• Where is Invenio 3 going.pdf (English)
• Cap on va Invenio 3.pdf (Catalan)

Functionality of our systems¶

• Invenio functionality at UAB
• Extra functionality at UAB

• Invenio functionality at JOIN2
• Extra functionality at JOIN2

• Common grounds between UAB and JOIN2

Requirements for the next system¶

• Requirements at UAB
• Requirements at JOIN2

• Common requirements for UAB and JOIN2

Invenio alternatives¶

My understanding (Ferran Jorba) is that we should not provide an encyclopedic list of characteristics of those alternatives; a valid link (or links) should suffice for that. Just a quick summary and the reasons why they are, or are not, a valid Invenio alternative.

At UAB we spent part of 2018 evaluating different free softwares to choose an Invenio alternative for smaller collections that need to be hosted in our university. That's why we are somewhat familiar with what exists out there. We followed those guides: http://www.rubenalcaraz.es/pinakes/software-libre/software-libre-para-bibliotecas-archivos-y-museos-2015/, http://www.rubenalcaraz.es/pinakes/software-libre/software-libre-para-bibliotecas-archivos-y-museos-2016/ plus other alternatives not listed there, like EPrints or Koha (by the way: we choose Omeka Classic).

• Invenio3

• Muscat
  • RISM vs CERN
  • Why our next software has to be a Ruby on Rails application
  • Ruby for Invenio admins
  • Rails for Invenio admins
  • Solr for Invenio admins
  • Blacklight for Invenio admins
  • Blacklight Summit 2020
  • Authors vs composers in Muscat
  • Muscat for Invenio admins
  • Vertical relations in Muscat
  • Record types, document types, authorities, fields and relations in Muscat
  • Document types and cataloguing templates in Muscat
  • Com modificar les plantilles de catalogacio de Muscat
  • How to create Invenio collections in Muscat
  • Muscat Ruby on Rails external consulting
  • Blacklight collections creation and installation notes
  • Per què apostem per Muscat
  • Muscat status reports
  • Prioritats en la implementació de Muscat
• Omeka
• Dataverse
• Evergreen
• Koha
• Folio
• OJS
• LibreCat
• Hosted Solutions

Traditional repository systems¶

• Dspace
• EPrints
• OPUS4

Felicitacions¶

• https://github.com/rism-digital/muscat/blob/develop/app/views/muscat_news/_20240205_muscat_10.ca.md (al Ferran Jorba i al seu equip)