Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
tidied some formatting in technical/reference which was creating mark…
…down syntax colouring problems in editors
  • Loading branch information
mrshll1001 committed Oct 18, 2023
commit 1ccd942376bada24a19eefcb410a997be355d858
10 changes: 5 additions & 5 deletions documentation/technical/reference.md
Original file line number Diff line number Diff line change
Expand Up @@ -329,7 +329,7 @@ The 360Giving Data Standard requires you to provide information on when a grant
There are three different rules for validating dates:

##### Full dates (Award Dates and Transaction Dates)
The ```Award Date``` **must** provide a full date, including year, month and day in YYYY-MM-DD format (e.g. 2017-04-02 for the 2nd April 2017).
The `Award Date` **must** provide a full date, including year, month and day in YYYY-MM-DD format (e.g. 2017-04-02 for the 2nd April 2017).

In some cases, award date data exported from grant systems includes the time of the grant, using a date-time format (e.g. 2017-04-02T16:45:00Z - a grant made at 4.45pm).

Expand All @@ -350,18 +350,18 @@ In some cases, award date data exported from grant systems includes the time of

Other events in the lifetime of a grant, such as for when the funded activity will take place, may include less specific date information. Funders should aim to be as specific as they can be, but do not need to guess at the particular day or month when an activity will take place if they are not certain or do not yet know.

Dates in the ```Planned Dates``` and ```Actual Dates``` groups should be provided in YYYY-MM-DD format, but the day or the day can be dropped or on the year provided (e.g. YYYY-MM or YYYY).
Dates in the `Planned Dates` and `Actual Dates` groups should be provided in YYYY-MM-DD format, but the day or the day can be dropped or on the year provided (e.g. YYYY-MM or YYYY).

For example, if an application only indicates that a project will start in May 2019, then the ```Planned Dates:Start Date``` value may be '2019-05'.
For example, if an application only indicates that a project will start in May 2019, then the `Planned Dates:Start Date` value may be '2019-05'.

It is up to users of the data to judge how to interpret dates which only include a year, or year and month. Different applications and analysis may require different judgements.

##### Date-time (Last Modified dates)
All rows in a 360Giving spreadsheet, and all objects in the JSON structure, can have a ```Last Modified``` date.
All rows in a 360Giving spreadsheet, and all objects in the JSON structure, can have a `Last Modified` date.

If used, this must always be in full date-time format so that if multiple updates take place on a single day, consuming applications can work out which version to use.

``` eval_rst
```eval_rst

.. hint::
You can set Excel to present a date column as a full date-time using the custom format of "yyyy-mm-ddThh:mm:ssZ". If you also set the formula for the entire column to ```=Now()``` then this value will be refreshed automatically every time you save the file.
Expand Down