Understand the philosophy of CollectiveAccess, navigate Providence, create a first record. The minimum needed to speak the same language as your cataloguers.
Day-to-day mastery of the interface: multi-criteria search, access control, sets, controlled lists, batch import, Joconde export for Musées de France.
Installation profile setup, screen configuration, user and rights management, import-export, day-to-day supervision. Full autonomy on your instance.
REST/GraphQL APIs, plugins, third-party integrations (IS, EDM, websites), Pawtucket themes. To go beyond configuration and extend the platform.
From the moment your data starts being migrated, your team is exposed to the structuring choices: data modelling, controlled lists, screens. That is our first chance to explain the « why » behind each decision — training has already begun.
2 to 3 days on-site or online, depending on your context. For Musées de France, a dedicated day on Joconde export and the decennial collection audit. Theory and hands-on practice on your real dataset — no textbook examples.
Your team catalogues, configures and imports — without us. A hotline is available when things get stuck. This is the phase when the real questions emerge: « how do I do this when… », « why does this field refuse… ». We log them for the next step.
A day to answer the questions that have piled up, dig into under-used features, automate what can be automated. By this stage your team knows what it wants — training becomes targeted and operational.
Familiarity with your institution's documentary principles. No prior IT skills required beyond standard web use.
Have completed the Cataloguers training, or have used CollectiveAccess as a user for at least 3 months.
Cataloguing in a Musée de France. Familiarity with the institution's statutory inventory.
Intermediate PHP, basic SQL and HTTP, Git. A development machine with a working CollectiveAccess environment.
Have completed initial training. Have catalogued regularly for 3 to 6 months.
During the migration phase, the team is involved in the modelling decisions. The screens they will work with are validated together. By the time the software arrives, it no longer feels foreign.
On-site initial training on the real dataset. Theory and practice in alternation, two trainers present so no one falls behind. By the end, every team member has entered their first ten records.
The team catalogues, imports and configures. The hotline is open for blockers — used 6 times over the period. Recurring questions are logged.
A day to answer the 40 accumulated questions, present three under-used features (dynamic sets, OAI, configurable exports) and lay out a 6-month roadmap.