# Common Terms
Here we define some of the common terms we use when working with Murmurations.
An Aggregator is any site which uses information from the Murmurations Index to present users with a collection of data, such as a map or directory. The Murmurations WordPress Aggregator is a WordPress plugin which makes it simple for content aggregators to create maps and directories using data from the Murmations Index using Wordpress. See for example, the Community Currency Alliance Map (opens new window) which features details of community currency projects around the world, all of whom have published Murmurations profiles according to the complementary currency schema (opens new window), in the Library. See more details about the Wordpress Aggrator Plugin in the developer docs.
A Field is a unit of data in Murmurations. It's like the header column in a spreadsheet or database table: first name, last name, email address, description, etc. Fields define the type (e.g., string, number, date, etc.) and validation rules for data. See the
primary_url field (opens new window) as an example.
The Murmurations Index keeps track of all the Nodes (via their Profiles) in the network. Whenever an entity updates its Profile it tells the Index. Aggregators frequently query the Index to find Profiles using their Schemas along with changes to existing Profiles, enabling them to provide up to date information in their maps, directories and content aggregators.
# Murmurations Protocol
The Murmurations Protocol, which we also just call Murmurations, is a standardised, open source set of rules designed to enable decentralised collaboration at scale. Murmurations uses existing standards such as JSON Schema (opens new window) to help people, projects and organisations discover each other and share data across platforms and between networks. The ultimate aim of Murmurations is to accelerate the global transition to the regenerative economy (opens new window).
A Profile is a JSON (opens new window) document describing a Node (person, project, etc.), using one or more Schemas. Here's an example Profile describing The Open Co-op (opens new window), using the Organizations schema (opens new window). Think of a Schema as a form template and each instance of a completed form as a Profile. Multiple Profiles can be created against a Schema, just like multiple rows of data are stored in a database table or spreadsheet and arranged by their Fields.
# Profile Generator
The Murmurations Profile Generator (opens new window), or MPG for short, is a web application for creating Profiles. MPG automatically converts Schemas in the Library into forms to enable people to create the JSON documents for their Profiles. MPG can also host these JSON documents, which may seem an odd way to manage decentralised data, but is an important feature which makes the protocol accessible to people who can't host their own Profile data.
A Schema is composed of multiple Fields and is described using JSON Schema (opens new window), which defines a collection of data fields and explains how they should be used. Schemas validate JSON documents to check the data entered in a Profile matches the expected format. See the Organizations Schema (opens new window) as an example.