Skip to content

Updating the DUCC and TOS

Jump to bottom
Joel Thibault edited this page Dec 20, 2022 · 7 revisions

How to upgrade the Data User Code of Conduct (DUCC) or the Terms of Service (TOS) Agreements

What this does not cover

  • DUCC Version requirements
  • Terra TOS interactions

Request a Google Doc

When a request comes in to upgrade the DUCC or TOS, it may appear in PDF or Google Doc format. Ultimately we need it to be in HTML, but we have been unsuccessful in requesting that directly. We have a process for Google Docs, so please request this if you only have a PDF.

Convert the Google Doc

  1. Save the Google Doc in .docx format
  2. Open it in Microsoft Word (Broadies: you can request a Word install via BITS)
  3. For DUCC: Remove the Signatures section. We handle that in the UI directly. Make note of any changes there that you need to apply.
  4. Save the doc (without signatures, if applicable) as "filtered" HTML. Use a filename with no spaces (and a version number for DUCC). Examples:
  • aou-tos.html
  • data-user-code-of-conduct-v5.html
  1. Copy the HTML doc and its accompanying FLD folder into ui/public. DUCC: Do not remove older versions, because they are used to display the signed versions to users.
  2. Modify the reference to the HTML file, if it has been renamed:
  • DUCC: Add an object to VERSIONS in utils/code-of-conduct.tsx
  • TOS: TermsOfService in sign-in.tsx and app-routing.tsx

Test

Check the formatting by running Local UI using a variety of window sizes. For DUCC, also check that the signed version looks right, and that older signed versions are still viewable.

Processes which are not recommended

Converting the Google Doc to HTML directly

This does produce a usable result, but the formatting is different and it doesn't look as good.

Eyeballing the changes

These docs are carefully curated by legal/compliance teams. Let's not risk missing something important.

Clone this wiki locally