We've shipped our latest update with significant improvements to the MOON Object System, along with a complete migration to Svelte 5 across MOON, EXH.CAT, and our site.
Blueprint System Updates
The biggest change in this release is our expanded Blueprint system. While Blueprints have always been central to MOON, we've fundamentally rethought how they can work with object data.
Most collection management systems (CMSs) force you into rigid templates - one form, one way to view data. That approach breaks down quickly when dealing with complex collections where objects need to be viewed through different professional lenses.
At its core, our system lets you build the exact data structure you need, whether you're following established standards or creating your own.
You can structure data to align with:
- Museum standards like CDWA (Categories for the Description of Works of Art)
- Library and archival standards
- Your institution's specialized cataloging practices
- Custom frameworks for special collections
Blueprints define what information you need for an object. Think of them as templates for organizing information.
Every object starts with standard information in the Core Blueprint. From there, you can add specialized Blueprints depending on what you're documenting.
For example:
- A painting might have fields for artist, medium, and dimensions
- A document might have fields for author, date, and language
- A photograph might have custom metadata fields like "Photographer" or "Negative Date"
- A project might need fields for deadlines, status, and milestones
With Blueprints you can:
- Create custom fields for your specific needs
- Group related information together
- Make fields required
- Lock fields to prevent changes
- Choose from different field types (text, dates, numbers, select menus, etc.)
All your information stays connected and organized, making it easy to find and update later.
Key improvements:
Primary and Secondary Blueprints
Choose a primary Blueprint that defines your object's type (like Paintings or Textiles), then add secondary Blueprints as needed. For example, a painting can use the "Paintings" Blueprint as its primary type while also being part of "New Acquisitions" or included in a "Portraiture Exhibition" project. This flexibility lets you organize objects across multiple contexts without duplicating data.
Viewing Blueprints
Base Members can view the information that's important to them, while collaborating with colleagues working on the same object. For example, a curator can use a research-focused Blueprint, while a museum educator can use a Blueprint designed especially for an educational project.
Real-time Blueprint switching without data transformation or loss
Switch between different views of your object data instantly without worrying about data integrity. No need to save, reload, or transform data when changing perspectives. Your data stays exactly as it is, you just see it differently.
Contextual validation that adapts to each Blueprint's requirements
Each Blueprint can enforce its own data quality standards. Required fields, data formats, and validation rules adjust automatically based on the current context, ensuring data integrity while maintaining flexibility.
Selective field syncing to improve performance
The system only updates fields that have actually changed, making the experience faster and more responsive, especially when working with large collections or complex objects.
Maintain data relationships across different views
Related data stays connected no matter how you view it. References between objects, linked assets, and relationships between fields remain intact across all Blueprints, ensuring consistent data organization.
What this means in practice: Curators, registrars, and researchers can now access object data through views specifically tailored to their needs, all while collaborating in real-time. No more context-switching between systems or compromising on data organization.
- Switch views on the fly while maintaining core object data
- Add specialized blueprints as needed
All Data Updates
We've improved how the system handles historical object data. Fields that are no longer active in any Blueprint are now preserved in a dedicated "Retired Fields" section and can be deleted as necessary. This maintains access to potentially valuable historical information while keeping current data clean and organized.
You can now:
- View all object data across any Blueprint context
- Access historical field data in a dedicated section
- Remove retired fields when needed
One more thing... Member Presence
Now, you can see when Base Members are on the same page. We hope to expand this to messaging but for now, it's a nice little notice when working on the same content.
We're excited to see how you'll use these new capabilities in your work.