MRGI LENS / WORKFLOW FIELD GUIDE
Prepare an image collection for external use
Select images with recorded usage context appropriate to a defined distribution purpose.
01 / FROM INPUT TO HANDOFF
Follow the decisions.
This walkthrough describes the intended MRGI product behavior. The browser demo illustrates a small part of the workflow; it does not run the complete application.
- 01
Describe the use
- Start with
- A fictional external publication request.
- Work through
- State the audience and purpose before selecting assets.
- Result
- A clear distribution context.
- 02
Inspect the records
- Start with
- Sample images with internal, public, or unknown usage scope.
- Work through
- Identify records matching the request and hold uncertain records for review.
- Result
- A candidate selection with visible exclusions.
- 03
Review metadata
- Start with
- The selected set and export policy.
- Work through
- Choose which metadata should accompany the output and inspect the result.
- Result
- A reviewed distribution copy.
- 04
Record the release
- Start with
- The reviewed selection.
- Work through
- Retain the asset versions, stated purpose, and export settings.
- Result
- A distribution history for later review.
02 / INPUTS & INTERCHANGE
What travels with the work.
These are foundation formats and intended handoff contracts. Support and fidelity must be confirmed for each released build.
| Artifact | Role | Review consideration |
|---|---|---|
| RAW / photo sources | Catalog and development | Camera support and rendering fidelity need target validation. |
| Metadata records | Usage context | Records require provenance and human interpretation. |
| Image exports | Downstream creative work | Privacy-sensitive fields should follow the chosen export policy. |
A deliberate cross-app boundary
Send reviewed photo selections to Pixel and Layout, and preserve supporting distribution records with Evidence.
The intended handoff should identify the selected resource, its version, the destination, and the user’s authorization. A linked application should not inherit unrestricted file access.
Explore the connected applications ↗03 / BOUNDARIES & READINESS
Know what this example establishes.
- Recorded permissions may be incomplete, expired, or inaccurate.
- The preview uses synthetic records and illustrations.
- Removing metadata does not remove visual personal information from an image.
Development status
The source foundation is imported. Consent workflows and distribution rules are planned. Recorded permissions do not replace a legal review of rights.
Before a production release
Validate real-file behavior and platform support, implement the stated authorization and review rules, and document the tested acceptance scope. The interactive website is a product demonstration, not a release candidate for the application.
04 / PRODUCT QUESTIONS
The details that matter.
Does the app decide whether an image is legal to use?
No. The proposed workflow surfaces records and review requirements. Rights decisions remain with authorized people.
Can I work with a local library?
That is the intended model. Optional connected services should have an explicit scope rather than unrestricted library access.
Open-source foundation
Local catalogs, RAW development, metadata, faces, and batch export exist in LightCraft. Consent-aware distribution is the proposed MRGI focus. Read the credits and foundation mapping.
Keep exploring Lens.
Return to the product breakdown or try the local interactive example.