01
Free software
Free Software Foundation definition, 1985. Four freedoms: run, study, modify, redistribute. The political reading: a choice about who controls the tools.
GPL, AGPL, LGPL · CollectiveAccess, Linux, GIMP
1.02 · Practice · Open source
Panorama and comparison 2026
Open source,
free software,
cultural collections.
Free software, open source, free-of-charge: three terms people conflate. Four reasons the open-source route holds up over a decade of work. And a panorama of the tools usable in France and abroad to manage museum and archive collections.
In this page
- Free, open source, free-of-charge: why they're not the same.
- The case for open source, verified over ten years.
- CollectiveAccess, Omeka, Arches: who does what.
- Comparison with the six French proprietary vendors.
Three words, three meanings.
Before comparing tools, the terms need to be agreed on. A lot of confusion starts with conflating these three.
02
Open source
Open Source Initiative definition, 1998. Emphasises the engineering benefits of collaborative development. Technically: the same thing as free software.
MIT, BSD, Apache 2.0 · Omeka, PHP, Apache
03
Free of charge
Costs nothing to download. But with no access to the source code and no active community, you have no guarantee that it will still work in five years.
Windows freeware · « free tier » SaaS
Collection management software
Proprietary? Open source? Free?
Understanding what is at stake to make the right choice.
The proprietary model
Your data is entrusted to a black box.
You rent access, you depend on a single vendor, and the tool's evolution is out of your hands.
Open source
The hood is open: the source code is public.
A worldwide community of developers can audit it, secure it and improve it continuously.
Free software
It is first and foremost a matter of freedom, not price.
It legally guarantees 4 fundamental rights for your institution:
1. Use
2. Study
3. Modify
4. Share
Choose independence
For your collections management, requiring free software
means guaranteeing the long-term durability and sovereignty of your cultural data.
Four reasons
that hold up over time.
What you can verify after five years of usage, not just at purchase time.
01
Your data stays under your control
When a proprietary vendor goes bankrupt or gets bought, customers find themselves with a database they can no longer exploit without an expensive migration contract. With open-source software, your data is in an open format and the code is public — you can hand over to another integrator or take the codebase in-house.
02
No per-user licence
A cataloguing project mobilises a varying team: salaried curators, registrars, external photographer, doctoral candidates, consulting dealer. With per-user SaaS billing, that headcount becomes an annual budget item to argue over. With CollectiveAccess, you decide on your accounts without a licence ceiling.
03
Pereniality built in
CollectiveAccess has existed since 2003. Whirl-i-Gig (Brooklyn) maintains the core; independent integrators extend it across two dozen countries. If one actor disappears, the code remains. That's the key difference with a proprietary vendor whose survival is conditioned on yearly revenue.
04
Digital sovereignty aligned with public sector mandates
France's SILL (Socle Interministériel des Logiciels Libres, code.gouv.fr) lists the open-source tools recommended for the State. Cybersecurity authorities and the Ministry of Culture have pushed for years for public institutions to favour software where they control the hosting and the code.
Five open-source tools
in actual use.
Each has its niche and its limits. Stated as they are, not as we'd like them to be.
CollectiveAccess
Whirl-i-Gig (Brooklyn) — international community, French integration via idéesculture
Museum and archival collection management — both scientific cataloguing and public publication. 14 record types, Getty vocabularies integrated, Musées de France plugins.
Limitation: Requires an integrator for setup and configuration. Not adapted to collections under a hundred objects.
Omeka (Classic / S)
Roy Rosenzweig Center for History and New Media, George Mason University
Public-facing publishing, virtual exhibitions, web-led collection valorisation. Strong digital humanities community. Featured snippet on « free collection software museum » via framalibre.
Limitation: Scholarly cataloguing depth more limited than CollectiveAccess. No French Museums regulatory module or decennial inventory features.
ICA-AtoM / AtoM
International Council on Archives + Artefactual Systems
Standardised archives ISAD(G), EAD, EAC-CPF. Built for departmental, municipal and corporate archive services.
Limitation: Archive-centric; doesn't cover museum object registry nor wide public web publishing.
Arches
Getty Conservation Institute + World Monuments Fund
Archaeological and architectural heritage, historic sites, built heritage mapping. Highly specialised.
Limitation: Not a museum collection management tool in the traditional sense. Steep technical learning curve.
Wikibase
Wikimedia Deutschland (the platform behind Wikidata)
Linked open data, semantic web, persistent identifiers. Used by some museums to publish authority records.
Limitation: Not a full cataloguing tool, more of a complement. Requires a team comfortable with the semantic web.
CollectiveAccess vs Omeka.
The two open-source heavyweights of collection management. Not a fight: each one serves a distinct target.
CriterionCollectiveAccessOmeka
Scholarly cataloguing depth
14 linked record types. Fields customisable without touching code. Getty / Wikidata controlled vocabularies built in.
Flat model: items + collections. Community extensions for deeper structure.
French Museums regulatory compliance
In-house museesDeFrance plugin: regulatory lock, SMF-conformant registers, decennial inventory, PV.
No dedicated module. SMF compliance possible but to be built end-to-end.
Public French documentation
documentation.ideesculture.com — full user guide in French, regularly updated.
Documentation primarily in EN, active but scattered French community.
Historical target
Art, history, ethnography, archaeology museums; institutional archives; private foundations.
Academic libraries, learned societies, DH (Digital Humanities) projects, smaller publication-led museums.
Setup
Requires an integrator for initial configuration. Not suitable for self-hosting without expert support.
Possible to install in a few hours for a simple project. More accessible for institutions without dedicated IT.
Against the six proprietary vendors.
Snapshot of the French GLAM market, audited solution by solution on 14 May 2026. Each has real strengths. None occupies the open-source territory.
Micromusée
Axiell France
Historic French reference (1989, acquired by Axiell). Thick client v7, OPAC web sold separately. Modular paid model, each brick adds to the bill.
Flora
Decalog (Yoni group)
Full-web, multi-vertical (museums, libraries, businesses). Used by the French Ministry of Culture. No dedicated catalogue raisonné module.
S-Museum
SKINsoft (Besançon)
12-product suite, six languages, full-web. Efficient SEO strategy via indexable case studies. Pricing not public.
Coeli
Coeli Platform (ES/CAT)
Fast-growing in France. Aggressive marketing: featured snippet on « best museum software » across several Google PAAs.
WebMuseo
A&A Partners (Paris)
Rich suite (WebMuseo + ActiMuseo on FileMaker + ARTéo + ARTreport + WM-Récolement). Prestige clients (Pasteur, Sorbonne, Picasso). ActiMuseo still on a FileMaker stack.
MuseumPlus
zetcom (Bern, CH)
International, 25 years old, 900+ museums worldwide including the Louvre (78,000 works). Limited FR presence: 0 ranked keyword in France at 2026-05-14. SaaS starting around €500/month for 5 users.
Audit finding (14 May 2026): none of the six proprietary vendors appears in the top 10 SERP on « logiciel libre gestion collections musée », nor on « alternative open source à X ». The field is wide open.
idéesculture, CollectiveAccess integrator in France.
Audit, setup, data migration, training, sovereign hosting and long-term maintenance. On the French GLAM open-source niche, we are the longest-running team.
Since
2012
idéesculture founded — dedicated CollectiveAccess practice in France.
Institutions
107
Museums, archives, specialised libraries, foundations and ministries supported since 2012.
Public repositories
69
Plugins, integrations and tools maintained on github.com/ideesculture. GPL / BSD licenses depending on the project.
Documentation
open FR docs
documentation.ideesculture.com — CollectiveAccess user guide in French, freely accessible.
§ 06.1
Migrating from a proprietary tool.
Six stages — variable in duration, not in method.
Audit of the current system
Reading the existing data schema, identifying business fields, spotting specifics (in-house nomenclatures, date formats, hierarchies). The stage that maps out what migrates as-is, what needs transformation, and what must be re-entered.
Business framing
Mapping the source schema against the CollectiveAccess editor screens for your use case. Also where latent decisions get made: keep the historical nomenclature or align on POP/Joconde? What level of decennial inventory do we reintegrate?
Mapping and cleanup
Conversion from XLSX, CSV, XML, MARC, FileMaker, MySQL. Detection of duplicates, mixed fields, non-normalised dates. Plenty of conversations with your cataloguers during this phase — that's normal.
Import and validation
Import into a staging instance, object-by-object verification on a sample, adjustments. Several back-and-forth iterations are the norm.
Team training
Cataloguers, administrators, sometimes developers if a third-party integration is planned. Sessions by role, on your real database, not on a case study.
Go-live
Effective switch, decommissioning of the old system, hotline open for the first weeks. At D+90 and D+180, we come back for the accumulated questions.
Frequently asked questions.
The questions that come up in initial conversations with institutions considering the move to open source.
Free software, open source, free of charge: what's the difference?
Technically, free software and open source mean the same thing: software whose source code is public and modifiable. The difference is philosophical. « Free software » (Free Software Foundation, 1985) emphasises user freedoms. « Open source » (Open Source Initiative, 1998) emphasises the engineering benefits of collaborative development. « Free of charge » says nothing about the code: a freeware can be closed, and free software isn't necessarily free to deploy.
What's the best free software for museum collection management?
For collections — museum, archival or foundation — that require serious scholarly cataloguing, CollectiveAccess is the best-established option in France. For smaller publication-led projects, Omeka can fit. For ISAD(G)-standard archives, ICA-AtoM is more natural. For archaeological sites, Arches covers the domain specifics better.
Why choose free software over a recognised proprietary vendor?
Three reasons come up repeatedly with our clients: perenniality (the code stays public if the vendor changes or disappears), data control (your files and your server, not a cloud you don't have access to), and licence cost (no per-user billing).
Is free software compliant with French Museums regulatory requirements?
CollectiveAccess paired with idéesculture's museesDeFrance plugin is. The plugin locks inventory entries once recorded, manages the decennial inventory, generates the PV (procès-verbal), and produces registers compliant with the Service des Musées de France. The plugin is used by labelled Musées de France (Musée André Voulgre, COR Ouest Rhodanien, Musée Malartre).
Does open source mean the project is free?
No. The software is freely downloadable and runnable, but a professional project — audit, setup, data migration, training, hosting, maintenance — requires expert time that integrators bill for. Over ten years, licence savings remain significant.
Can I migrate from Micromusée, Flora, S-Museum, WebMuseo or MuseumPlus?
CollectiveAccess accepts XLSX, CSV, XML, MARC, FileMaker, MySQL imports and ingests most formats those vendors can export. The migrations actually performed by idéesculture to date concern Excel, FileMaker, AtoM and Micromusée. For Flora, S-Museum, WebMuseo, Coeli or MuseumPlus, migration is technically feasible but requires a preliminary audit of the exports your current vendor provides. To discuss case by case.
What's the total cost of ownership of free software over 10 years?
Highly variable depending on project size and accompaniment scope. Initial investment (setup, migration, training) is often comparable to a proprietary deployment. Over time, the absence of per-user licences and the ability to change integrator without changing the tool keep the cumulative bill lower. Ask us for a scoping note for your case — it's free.
What happens if idéesculture disappears?
Your CollectiveAccess installation keeps running — that's precisely the point of open source. The code is public on GitHub (whirl-i-gig/ca_providence + our 69 ideesculture/* repositories). Another integrator can take over maintenance. Your data stays in a standard MySQL format that you control.
Does the French Ministry of Culture recommend free software for collections?
The Ministry doesn't endorse a specific tool but maintains the public list of software used by Musées de France. The Socle Interministériel des Logiciels Libres (code.gouv.fr/sill) more broadly lists open-source tools recommended for the State. Public policy: favour open source where a functional option exists, and evaluate digital sovereignty on every IT purchase.
Who does idéesculture actually work with today?
107 institutions accompanied since 2012, from major national museums (Musée d'Orsay, Quai Branly, Villa Médicis, INRAP) to municipal museums and écomusées, as well as private foundations, archaeology operators and archive centres. Details on our References page.
Talk to idéesculture
A project to scope?
Audit of the current system, estimate of migration scope, budget framing. The first conversation is free and leads to a written scoping note that belongs to you — even if you then decide to work with someone else.