Enterprise DNA

Instead of PoolParty

Stop renting PoolParty. Own your terminology system.

We build your version around how your editors work, bring your PoolParty vocabulary across and run the agreed system for you. Keep the term identities, the relationships and the reasons behind every change.

PoolParty is now part of Graphwise. Its pricing link leads to a platform quote, with no current numeric licence price published there.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

Read the quote against the work

A platform quote can cover much more than your vocabulary desk

Graphwise presents suites, sizing, connectors and services. Separate the terminology work you need each week from the wider platform you are buying.

paid

A price supplied by sales

The current pricing destination asks for a quote. Compare your actual renewal with a defined scope for the system you want to own.

layers

A suite around the vocabulary

The platform combines terminology modelling with storage, automation and analysis. Your editors still need a clear record of terms and review decisions.

straighten

Sizing in the proposal

Standard, Extended and Large appear in the platform options. Ask which size and components your quoted service includes.

extension

Connected content systems

The platform lists connections for Microsoft 365, Tridion and Adobe Experience Manager. Identify which connections your business depends on before scoping a switch.

support_agent

Support and maintenance

Support, maintenance and extended maintenance appear among the service options. Decide who will operate your own database and handle changes.

assignment

Implementation services

Quick Start and accelerator services are listed alongside the platform. Your own version also needs a deliberate import, reconciliation and handover.

Your owned terminology workflow

Keep the term, its meaning and the review together

Vocabulary

A stable identity for every term

Labels change. Keep the identity and meaning that your business records depend on.

  • check Keep the original term identities from the source export
  • check Record preferred names, synonyms and hidden search labels by language
  • check See the broader terms above any concept
  • check Retire a term with a named replacement and keep its history

Quality

Find conflicting words before the next release

Combine the language gaps with ownership and review dates so the next action has a person attached.

  • check List missing names in the languages your scheme requires
  • check Find labels that identify more than one active term
  • check Reject hierarchy cycles and conflicting relationship types
  • check See overdue terms beside their unresolved editorial requests

Editorial decisions

A changed term needs another look

The review record follows the current version, so a later edit cannot rely on an old approval.

  • check Give change requests an owner and a due date
  • check Record the decision and reason for each request
  • check Return changed terms and affected relationships to review
  • check See draft terms that have gone untouched for a month

Release records

Keep a copy of what the editors agreed

Record an internal vocabulary release only when the quality checks and reviews are complete.

  • check Check unresolved requests and missing approvals together
  • check Keep a dated copy of terms, labels and relationships
  • check Produce a vocabulary register and editorial review brief in your brand
  • check Compare your current work with the recorded release without overwriting it

Make it yours

Design your own PoolParty replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from PoolParty. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your PoolParty replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your PoolParty data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Taxonomy for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Taxonomy for Claude Code

Connected to your own database

Which terms need an editor, and what is still open?

code | name | owner | status | review_due | open_requests | reason --------+---------------+-----------+--------+------------+---------------+------------------- QUALITY | Water quality | Mara Chen | draft | 2026-10-20 | 1 | overdue review SUPPLY | Water supply | | draft | 2026-10-30 | 0 | draft needs review

Ask it anything

Ten questions your vocabulary desk answers

These questions combine your editorial rules and working history. Each is answered by the demo today.

chat_bubble Which overdue terms also have open requests?
chat_bubble Which language gaps belong to overdue terms?
chat_bubble Which labels mean more than one thing?
chat_bubble Which active terms lack a definition?
chat_bubble Which active terms have no owner?
chat_bubble Which active terms point to a retired term?
chat_bubble Which terms have more than one broader parent?
chat_bubble Which draft terms have gone untouched for a month?
chat_bubble Which requests are overdue, grouped by owner?
chat_bubble Which schemes have no recorded release?

Switching

How to switch from PoolParty

A move usually involves exporting your vocabulary, mapping it into the new database, checking the import, then running both systems together before you retire PoolParty.

  1. 1

    Export your records

    Use PoolParty’s export options to get your vocabulary records in structured RDF/JSON or CSV. Include the terms, labels, definitions and relationships you need to carry over. PoolParty supports vocabulary exports in these formats. If your account does not show the option you need, check with PoolParty before planning the import.

  2. 2

    Map and preview

    The new database reads one unzipped RDF/JSON export or a CSV extract mapped to its fields. Preview the import before applying it. The free version uses a command-line workflow, not a web front end. If that is not how your team wants to work, agree the installed version and any editing screens with Enterprise DNA before switching.

  3. 3

    Check flagged records

    Review the preview’s ignored fields and compare the imported term and relationship counts with PoolParty. Example mappings are not universal, so check that your own columns and fields landed where you expect. Imported terms still need an owner, review date and approval. Changed source records stop for reconciliation, so resolve those rather than assuming they imported cleanly.

  4. 4

    Run both side by side

    Keep PoolParty available while your team uses the new database for a short period. Compare terms, labels, definitions, relationships and review decisions, and confirm editors can complete the work they need. Check any search service or live content connection separately, since these are not part of the free internal vocabulary desk and need to be scoped for your version.

  5. 5

    Switch off PoolParty

    Once the imported records and agreed workflow check out, make the new database your working record and stop editing in PoolParty. Confirm you have saved the export and know where the records you need are kept. Do not assume search services or content connections have moved with the vocabulary. Switch PoolParty off only after those dependencies and your team’s access to the new process are settled.

construction

Where the real effort goes

The effort is usually less about loading records than agreeing how your PoolParty fields map to the new records, which history and custom fields to carry, and which owners, languages, review dates and approval rules to set. Some fields need extra work, and imported terms still need review. If Enterprise DNA installs and runs the system, it handles the agreed mapping and reconciliation with you.

Not ready for a call?

Get your PoolParty switch plan by email

We will send you the step-by-step plan for moving your business off PoolParty, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Choose who builds and runs your version

Open source

Do it yourself

Free, MIT licence

  1. 1 Clone the repo, run npm install and npm run demo
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor
  3. 3 Preview your PoolParty RDF/JSON export or map the actual CSV headings
  4. 4 Reconcile the import, assign editors and run the review commands
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your vocabulary fields, languages and review rules
  • check Your PoolParty exports mapped and reconciled
  • check A web front end or a different stack if you want one
  • check Search and content connections scoped around the systems you use
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Your database and backups maintained
  • check Agreed connections and review reports kept working
  • check Changes handled as your terminology and business evolve
Book a discovery call

Questions

Instead of PoolParty, answered

Is PoolParty still the product I am comparing? expand_more

PoolParty is now part of Graphwise. The former price overview redirects to the Graphwise platform and asks for a quote. Compare the components and services on your current agreement with the vocabulary workflow you need.

Can you bring our existing terms and relationships across? expand_more

Yes, within an agreed mapping. PoolParty supports vocabulary exports in structured and spreadsheet formats. The free version reads a supported structured export or a mapped spreadsheet extract. We reconcile identities, languages and relationships, and review any custom fields that need extra work.

What about our search service and content connections? expand_more

Enterprise DNA can build agreed search and content connections into your version. We scope those dependencies before a switch, alongside any editing screens your team needs. The free version handles the internal vocabulary and review work.

How do we know an old approval is still valid? expand_more

Changes to a term or its relationships return the affected records to review. A release check looks for missing approvals, overdue reviews, unresolved requests and quality gaps. The person making a decision is recorded by name, with a reason. Verified sign-in and additional approval controls are work to scope for your version.

Do we keep the system if we stop the service? expand_more

You own the database and the open-source base. Your vocabulary and operating records can be exported. Enterprise DNA charges one setup fee and then a retainer for the agreed build and operation, with the handover and ongoing responsibilities defined together.

Bring your vocabulary and your current quote

Book a 30-minute call with Sam. We will work through the terms, review rules and content connections you rely on, then define the version Enterprise DNA can build and run for you.

Book a discovery call Get the free version

Taxonomy for Claude Code is free and open source, published by Enterprise DNA.

Done paying for PoolParty?

Get your version built