# Standing Technical Meetups

**URL:** <https://forum.openreferral.org/t/standing-technical-meetups/454>\
**Category:** Technical\
**Created:** [November 6, 2023, 10:39am UTC](https://forum.openreferral.org/t/standing-technical-meetups/454 "2023-11-06T10:39:49Z")\
**Posts on this page:** 1\
**Showing post:** 57

<div class="post-metadata">

**Author:** ![Dan-ODS](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openreferral.org/dan-ods/32/89_2.png) [@Dan-ODS](https://forum.openreferral.org/u/Dan-ODS)\
**Post date:** [February 25, 2025, 10:51am UTC](https://forum.openreferral.org/t/standing-technical-meetups/454/57 "2025-02-25T10:51:30Z")

</div>

### **Key Actions and Takeaways from the Standing Technical Meetup 02-12-2025**

#### **UK Update & Validator Deployment**

- Watch the [Meet the Early Adopters of Open Referral UK (ORUK)](https://email.newsletter.localdigital.gov.uk/tl/cl/eyJ2Ijoie1wiYVwiOjEwMzIyNCxcImxcIjoxNDYxMzY3NzEyNzU1MjM3NTksXCJyXCI6MTQ2MTM2NzgzODY3ODcyODkyfSIsInMiOiIyZGI0ZjVmNzJlOGI4MzExIn0) recording.
- Proposed validator deployment and associated website targeted for the end of March.
- UK validation to require minimal compliance with a low threshold of records.

#### **Validator Features & Considerations**

- Define **Full vs Partial validation** :
  - Partial: Subset of records, fields, or endpoints?
  - Consider developing a separate “sampler” tool for partial validation.

- Determine whether to **extend the UK validator or build a new one** :
  - Skyler: .Net approach seems straightforward.
  - Matt: Distinguish between schema validation (compliance) and data quality checks.
  - Kate & Skyler: Formatting and completeness ≠ quality.
  - Mike: Define key quality aspects—validity, completeness (for a use case), and accuracy.

Distinctions:

- **Partial vs Full** : Sample vs entire dataset.
- **Basic vs Complete** : Minimum validation vs complete spec/profile validation.
- **Spec Compliance vs Custom Quality** : Schema validation vs quality checks.
- **Syntactic Correctness vs Truthing** : Validation vs verification/provenance.
- **Schema vs Endpoint** : What level is being validated?

#### **User Feedback & Error Handling**

- Define minimum required feedback for users:
  - “Description of errors” and clear problem identification.

- Routine validation with automated notifications?
- Allow users to **revalidate after fixing errors**.

#### **Validator Accessibility & Future Planning**

- Interest in **downloading and running a validator locally** (tabled until April).
- Added to [bike rack](https://docs.google.com/document/d/1SYmsSa_U8uQKZW0zhEq8H6CNttNeWPqP7BAV0HDJa2o/edit?tab=t.0#heading=h.73gepa5c3l9o)

#### **[Transformer proposal](https://forum.openreferral.org/t/hsds-go-types-and-constructors/597) (Interest? Questions?)**

- Stimulated a conversation around the initiatives general approach to community tooling which could involve the following:
  - Encouragement: To promote innovation
  - Input: To ensure alignment
  - Endorsement: To support uptake

#### **[Metadata API Enhancements](https://github.com/openreferral/specification/issues/524)**

- Discussion in the [forum thread](https://forum.openreferral.org/t/extra-metadata-with-api-feeds/572/5) developed into a [proposal](https://docs.google.com/document/d/1jy1wOShCNypl7OqAIuMTc80blxTBUn5_6YhjvOyF6LI/edit?tab=t.0#heading=h.ye0dggmm63xe)
- Consider record-level metadata in the next subversion.
- Define “Organization” as publisher and align with “Contact” schema.

- Kate to work with us to further specify for longer term

---

_[View the full topic](https://forum.openreferral.org/t/standing-technical-meetups/454)._