Changes
On April 22, 2020 at 12:21:25 PM UTC, Digital Birmingham:
-
No fields were updated. See the metadata diff for more details.
f | 1 | { | f | 1 | { |
2 | "author": "Accounts Payable", | 2 | "author": "Accounts Payable", | ||
3 | "author_email": "foi.mailbox@birmingham.gov.uk", | 3 | "author_email": "foi.mailbox@birmingham.gov.uk", | ||
4 | "creator_user_id": "a7630b1f-64bd-4133-a8ad-402549370762", | 4 | "creator_user_id": "a7630b1f-64bd-4133-a8ad-402549370762", | ||
5 | "id": "7ad90c2a-cd7b-4d9b-8ef0-12e50ace4ff9", | 5 | "id": "7ad90c2a-cd7b-4d9b-8ef0-12e50ace4ff9", | ||
6 | "license_id": "uk-ogl", | 6 | "license_id": "uk-ogl", | ||
7 | "maintainer": "Birmingham City Council", | 7 | "maintainer": "Birmingham City Council", | ||
8 | "maintainer_email": "Accountspayable@birmingham.gov.uk", | 8 | "maintainer_email": "Accountspayable@birmingham.gov.uk", | ||
9 | "metadata_created": "2020-04-22T12:19:09.277410", | 9 | "metadata_created": "2020-04-22T12:19:09.277410", | ||
n | 10 | "metadata_modified": "2020-04-22T12:21:23.312206", | n | 10 | "metadata_modified": "2020-04-22T12:21:24.870667", |
11 | "name": "february-2020-purchase-card-transactions", | 11 | "name": "february-2020-purchase-card-transactions", | ||
12 | "notes": "Under the Code of Recommended Practice for Local | 12 | "notes": "Under the Code of Recommended Practice for Local | ||
13 | Authorities on Data Transparency, councils are encouraged to publish | 13 | Authorities on Data Transparency, councils are encouraged to publish | ||
14 | all corporate purchase card transactions.\r\n\r\nWe already publish | 14 | all corporate purchase card transactions.\r\n\r\nWe already publish | ||
15 | details of all our relevant expenditure of more than \u00a3500 within | 15 | details of all our relevant expenditure of more than \u00a3500 within | ||
16 | our Payments to Suppliers page, and will continue to do so. However, | 16 | our Payments to Suppliers page, and will continue to do so. However, | ||
17 | in the spirit of the Code, the Council started publishing all purchase | 17 | in the spirit of the Code, the Council started publishing all purchase | ||
18 | card transactions, regardless of value, from the April 2014 card | 18 | card transactions, regardless of value, from the April 2014 card | ||
19 | statement. The information will be published monthly.\r\n\r\nAs with | 19 | statement. The information will be published monthly.\r\n\r\nAs with | ||
20 | our payments to suppliers, we aim to be as transparent as we can, but | 20 | our payments to suppliers, we aim to be as transparent as we can, but | ||
21 | in some cases we will need to respect information that could be seen | 21 | in some cases we will need to respect information that could be seen | ||
22 | as commercially sensitive or where the payment relates to vulnerable | 22 | as commercially sensitive or where the payment relates to vulnerable | ||
23 | young people or adults. In these cases information is withheld as it | 23 | young people or adults. In these cases information is withheld as it | ||
24 | is personal data. For further information about personal data, please | 24 | is personal data. For further information about personal data, please | ||
25 | see birmingham.gov.uk/foi.\r\n\r\nIf you require further information | 25 | see birmingham.gov.uk/foi.\r\n\r\nIf you require further information | ||
26 | about any of the payments, please contact | 26 | about any of the payments, please contact | ||
27 | foi.mailbox@birmingham.gov.uk setting out the details of the payment | 27 | foi.mailbox@birmingham.gov.uk setting out the details of the payment | ||
28 | and what additional information you require. Such request will be | 28 | and what additional information you require. Such request will be | ||
29 | handled under the Freedom of Information Act 2000, and the Council | 29 | handled under the Freedom of Information Act 2000, and the Council | ||
30 | aims to be able to provide a response to your query within 20 working | 30 | aims to be able to provide a response to your query within 20 working | ||
31 | days.", | 31 | days.", | ||
32 | "owner_org": "4eda0082-f593-489e-b66a-8fe8274cfc94", | 32 | "owner_org": "4eda0082-f593-489e-b66a-8fe8274cfc94", | ||
33 | "private": false, | 33 | "private": false, | ||
t | 34 | "revision_id": "bc9679a4-06f5-4bec-b7fd-31cb6d03f91e", | t | 34 | "revision_id": "efcb0a81-b253-49ea-a732-bc411a4081fd", |
35 | "state": "draft", | 35 | "state": "active", | ||
36 | "title": "February 2020 Purchase Card Transactions", | 36 | "title": "February 2020 Purchase Card Transactions", | ||
37 | "type": "dataset", | 37 | "type": "dataset", | ||
38 | "url": "Birmingham City Council", | 38 | "url": "Birmingham City Council", | ||
39 | "version": "1.0" | 39 | "version": "1.0" | ||
40 | } | 40 | } |