JSON in, directory out
Turn your JSON data into a manageable directory.
Start with the export you already have. Bobby Directory reads its shape, proposes readable names, and shows you what a profile would look like before anything is created.
- This release is a demonstration. No file of yours is opened or read.
- Nothing you type is parsed, transmitted or kept.
- No address is retrieved, no image downloaded, no command executed.
This importer is a demonstration. It does not process your data.
Every control below is inactive. No file is opened or read, nothing you type is parsed or kept, no address is retrieved and no command is run. Choose View the demonstration to see the intended result, produced from a bundled example file that ships with this website.
Paste the export straight into the field.
This field is read only and holds a harmless example. Nothing typed or pasted into this website is parsed, transmitted or kept during this phase.
Interface preview. This release describes structure. It does not create a directory, store a file, or contact any remote address.
Suitability
You see the result before you commit
The preview reports the record count, the detected fields, the proposed roles, the unresolved keys and the problems that would need a decision.
The figures below come from a bundled demonstration file of fictional garden centres. No real record, customer or metric is shown anywhere on this site.
Suitability preview
Generated from the bundled demonstration file. 4 records, 13 fields.
Sample profile
Willow Lane Garden Centre
- City
- Harlow
- Country
- GB
- Website
- https://example.invalid/ ...
- Telephone
- Redacted until mapping is confirmed
- Email address
- Redacted until mapping is confirmed
- Categories
- 2 references
- Images
- 1 reference, not retrieved
Inventory
- Identifier: id
- Media references: img_urls, not retrieved
- Relationships: cat_ids
- Unresolved: meta.source
Warnings
- cat_ids references categories that are not present in this file.
- rating_avg has no scale definition. A range will need to be confirmed during mapping.
- One record has an empty media array.
Field roles shown here are proposals. Nothing is created until a mapping is confirmed inside a workspace.
How it works
Four steps, and you stay in control of each one
01
Bring your export
Upload a file, paste the JSON, or describe the endpoint that produces it. The structure is read in your browser.
02
See what it would become
Every key is listed with a readable name, a type, a role and how often it is filled, plus what would need attention.
03
Confirm the mapping
You choose the identifier, the record path and the readable names. Nothing is created until you confirm.
04
Manage and publish
Moderate profiles, invite the people who run them, and publish one profile at a time.
Any subject
A directory is not only a list of companies
Profiles are described by typed properties rather than a fixed schema, so a directory of people, animals, places or objects uses the same machinery.
Read the use casesPeople directories
Members, practitioners, alumni and speakers.
Business directories
Salons, garden centres, clinics, workshops and studios.
Place directories
Venues, sites, routes and facilities.
Animal and object registers
Breeders, kennels, collections and equipment.
Profile Studio
The people who run a profile get their own place to work
Invited collaborators manage only what they were granted. Access is scoped to a single profile, it can be time bound, and every change is proposed rather than published.
Separation of surfaces
- Public website
- Marketing, documentation and published directories.
- Profile Studio
- Invited profile collaborators only.
- Workspace Console
- Directory owners, stewards and moderators.
- Platform Admin
- Platform operation, held separately from workspace work.
Bring the export. Keep the control.
Create an account to prepare a workspace, or read how the importer treats your data.
