From 82cac1175a3a7ddf78734226445a0ea238516981 Mon Sep 17 00:00:00 2001 From: Graham Hukill Date: Tue, 27 Feb 2024 14:45:18 -0500 Subject: [PATCH] Mard ADR 0002 as approved with decision --- docs/adrs/0002-field-for-data-type-form-information.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/adrs/0002-field-for-data-type-form-information.md b/docs/adrs/0002-field-for-data-type-form-information.md index 60c28c8..3328d10 100644 --- a/docs/adrs/0002-field-for-data-type-form-information.md +++ b/docs/adrs/0002-field-for-data-type-form-information.md @@ -6,7 +6,7 @@ Date: 2024-02-15 ## Status -Proposed +Approved ## Context @@ -210,7 +210,7 @@ Cons: * may require explanation of the facet mapping in the UI documentation * may require updates of other transform classes for consistency -#### Option 5 - Map `format` to "Format" filter, map 'content_type' to "Data Type" filter +#### Option 5 - Map `format` to "Format" filter, map `content_type` to "Data Type" filter In this approach, there would be **no** immediate data model changes. As outlined above, both the pre-existing `format` and `content_type` fields would be sufficient for mapping data from the Aardvark records in such a way to support "Format" and "Data Type" UI filters. @@ -243,7 +243,7 @@ Examples across multiple sources: ## Decision -TBD +The decision is to go with Option 5: Map `format` to "Format" filter, map `content_type` to "Data Type" filter. ## Consequences