Participation

The author(s) certainly do not know everything there is to know about libraries or analytics. There will be better explanation, methods, examples, exercises, etc than have been presented here. An ongoing, collaborative effort will improve the quality of these resources.

Please read the code of conduct if you haven’t already done so. It’s important for this community to abide by it.

libtics.org is open source

All the material is open source and licensed as CC BY-NC 4.0.

libtics.org is managed/developed like code

Well, más o menos. There are requirements, specification, coding, test, integration, deployment, issue tracking, etc. All backed up by version control at GitLab.

libtics.org code repository

Is at GitLab. There are a few component parts of the libtics project:

  • landing — Initial entry pages to the site.

  • aapl — The main material so far, Analytics for Alma, Primo and Leganto.

  • aapl-video — All the video tutorials for AAPL.

  • antora-ui — A clone of the default Antora user interface.

  • site-builder — The configuration for building using Antora locally and on Netlify.

  • utils — Some helpful bits and pieces for maintaining libtics.

  • dev-env — This repository contains configuration files for setup of a development environment for libtics.

How to contribute

You can take part in a number of ways. Firstly, there is the Zulip chat forum (under the Resources menu at the top right of the page). We are looking for any and all inputs via a variety of mechanisms detailed below.

Contact the authors

Get in touch directly via email or messaging. John’s details are here.

Raise issues

Issues can be raised using the tools on gitlab.com where the source for this material is held.

Create pull requests

Again via gitlab and git, a pull request can be raised to incorporate your changes. What’s a "pull request". It’s a package of your changes to the source code, made via git mechanisms, that are submitted for consideration to be merged into the repository.

Try out the development environment

Construct a development environment for libtics.org using the instructions in the repository at dev-env. You can use either docker or vagrant. Both work fine, both constructing a virtual machine or containerized development environment. I’m leaning towards docker being the "official" supported development environment.