Retired Item Dates

[AngelaFaulding]

269 has been fixed but it contains an issue relating to the "Retired date", where does it come from?

28/2/22 - Discussion with James: drop the "Retired Date" from the profiles.

[AngelaFaulding]

There is now no requirment to add a retired date, however this isn't showing correctly on the Orchestrator preview. This will be checked when the retirement processes are walked through with James. This will to be done once all the "create" processes are finished. DMDS also need to agree the business process of when a date is added, i.e. it will be added when a National Code/Deafult Code is retired but what is required when an item is retired.

[AngelaFaulding]

@cach1 - Will a date be added in the "Retired date" field for an item? If so, will it be the implementation date for a standard and publication date (release month) for a DDCN and patch?

[AngelaFaulding]

Wiki page started, but we need to confirm re the date and generally how to retire items, see #412

[cach1]

@AngelaFaulding for a dictionary data item (class, attribute, data element, business definition, supporting info) which is part of an Information Standard, it would be the Implementation Date of the standard. For a DDCN, thinking about the sort of thing we put in there - I think this might vary a bit - the publication of a DDCN on our page, isn't really linked to the incorporation in the dictionary release - so if a DDCN with a retirement in went up on our page, and we couldn't have a release for several months - the DDCN would still be the 'current position'. So in theory, should it be the date that we publish the DDCN on the DDCN web page, and not necessarily the date the DDCN is reflected in live dictionary?

Patch - these are always linked to a release so should reflect the release month I would say (01/xx/xxxx)

[AngelaFaulding]

Thanks @cach1. This will work for ISNs and patches (we known what patch the item will be in). We can test this out for a DDCN as during authoring we don't always know when the DDCN will be published.

[AngelaFaulding]

Text to be added to the Wiki:

• For an item which is part of an Information Standard, the retired date will be the Implementation Date of the standard
• For an item which is part of a Data Dictionary Change Notice (DDCN), the retired date will be the 1st of the month that the DDCN is published on the website
• For or an item which is part of a patch, the retired date will be the 1st of the month of the release patch , i.e. 01/##/####

[AngelaFaulding]

Issue can be closed as it has now been documented.

[AngelaFaulding]

For Kate and Angie to revisit.

[AngelaFaulding]

This needs looking at again.

• For an item which is part of an Information Standard, the retired date will be the Implementation Date of the standard This is OK.
• For an item which is part of a Data Dictionary Change Notice (DDCN), the retired date will be the 1st of the month that the DDCN is published on the website The author wouldn't always know when the DDCN will be published and what release it will go in
• For or an item which is part of a patch, the retired date will be the 1st of the month of the release patch , i.e. 01/##/#### The item wouldn't be retired on the 1st of the month as the release is always towards the end of the month

[AngelaFaulding]

22/10/24 - James agrees that the retired date is not used anywhere other than in a Term retirement. DMDS need to decide whether to use this as it is not required as there no history for this.

[AngelaFaulding]

Wiki to be updated to remove all references to retired dates (unless it is a Term) and it needs adding to the Decision Log.