knobit.org

C1 (3 points)

edu:Question

https://knobit.org/id/task/dso-retention-implementation/C1

Also as Turtle · JSON-LD · RDF/XML

dcterms:licensehttps://creativecommons.org/licenses/by/4.0/
owl:sameAshttps://bitbucket.org/reffa/ontology/id/task/dso-retention-implementation/C1
rdfs:labelC1 (3 points) en
schema:hasPartdso-retention-implementation C1: PJ-010 purging after 5 years against RR-010's 7, corrected to P7Y
schema:hasPartdso-retention-implementation C1: PJ-011 counting from dispute_closed_date, which DS-011 does not hold
schema:hasPartdso-retention-implementation C1: RR-013 period set by the platform team, raised with the records manager
schema:identifierC1
schema:position1
schema:textJobs held against their rules, 1 each. (a) PJ-010 purges card transaction records 5 years after settlement while RR-010 keeps them 7 years: named as a purge before the retention period ends and corrected to P7Y. (b) PJ-011 counts from dispute_closed_date, a field DS-011 does not hold, so the closure date cannot be computed: named, and the fix is the field added at source or a derivation agreed with the data owner (raised), not a silent switch to another field. (c) RR-013's period comes from a platform team decision, not the records schedule: named as a period set here and raised with the records manager, not kept as if valid and not replaced by a period of the answer's own. en

Used by

has questionCard platform retention - periods, triggers, holds, run records and archives (retention implementation skills)
schema:isPartOfdso-retention-implementation C1: PJ-010 purging after 5 years against RR-010's 7, corrected to P7Y
schema:isPartOfdso-retention-implementation C1: PJ-011 counting from dispute_closed_date, which DS-011 does not hold
schema:isPartOfdso-retention-implementation C1: RR-013 period set by the platform team, raised with the records manager