From beb92ba8b389c183c1fddd805b79b9dc3b7c9330 Mon Sep 17 00:00:00 2001
From: James McKinney <26463+jpmckinney@users.noreply.github.com>
Date: Sat, 31 Jul 2021 13:15:45 -0400
Subject: [PATCH] guidance: Add 5 remaining videos for publisher audience
---
docs/guidance/build.md | 8 ++++++++
docs/guidance/design.md | 4 ++++
docs/guidance/map.md | 8 ++++++++
3 files changed, 20 insertions(+)
diff --git a/docs/guidance/build.md b/docs/guidance/build.md
index e1309d908..91ce952da 100644
--- a/docs/guidance/build.md
+++ b/docs/guidance/build.md
@@ -1,5 +1,9 @@
# Build
+
+
+
+
This phase is about creating a new IT system, or updating an existing IT system, to implement your [mapping](map) and publish OCDS data.
Alternatively, if you don't have the capacity to create or update an IT system, you can consider reusing an existing [data collection tool](build/data_collection_tools). If you're reusing an existing tool, this phase is about customizing that tool to meet your needs and working out how to combine and publish your data. The [OCDS Helpdesk](../support/index.md#ocds-helpdesk) can help you to consider options for collecting, combining and publishing data.
@@ -60,6 +64,10 @@ Otherwise, you can consider the following methods:
## Establish your publication formats and access methods
+
+
+
+
OCDS data can be published in different formats and accessed using different methods.
It is best practice to provide data in multiple formats, so that as many users as possible can use the data without first having to transform it to their preferred format. In OCDS terms, this means [publishing both structured JSON data and tabular CSV or spreadsheet data](build/serialization).
diff --git a/docs/guidance/design.md b/docs/guidance/design.md
index 809dabbc6..827f84e36 100644
--- a/docs/guidance/design.md
+++ b/docs/guidance/design.md
@@ -1,5 +1,9 @@
# Design
+
+
+
+
This phase is about setting up your OCDS implementation to be a success.
On this page, you will find guidance on how to:
diff --git a/docs/guidance/map.md b/docs/guidance/map.md
index 341cfb793..d7319ab2a 100644
--- a/docs/guidance/map.md
+++ b/docs/guidance/map.md
@@ -1,5 +1,9 @@
# Map
+
+
+
+
This phase is about documenting your sources of contracting data, and documenting how that data "maps" to OCDS – that is, identifying which [data elements](https://en.wikipedia.org/wiki/Data_element) within your data sources match which OCDS [fields](../../schema/reference) and [codes](../../schema/codelists). The mapping phase is one of the longest and most important steps in the implementation process.
When starting out, consider working in parallel on the map and build phases, because the choices you make at the build stage might affect how you need to map your data. For example, your choice of architecture might determine whether you are able to publish a change history using releases and records.
@@ -48,6 +52,10 @@ map/localization
## Download the mapping templates
+
+
+
+
To make the mapping easier we provide templates to list the data elements within your data sources, and map them to either:
* OCDS [fields](../../schema/reference), using the [Field-Level Mapping Template](https://www.open-contracting.org/resources/ocds-field-level-mapping-template/) ([read the tutorial](https://www.open-contracting.org/resources/ocds-1-1-mapping-template-guidance/))