Alert users that their records are out-of-date, as they become out of date?
I have a construction_events table in an Oracle database. Users enter construction events into the table via GIS software.
For example, a user can enter a construction project for 2019.
The event_status would be entered as proposed.
Starts out as legit:
The record is legitimate at the time that it is entered. The user proposes a project for 2019 which makes logical sense.
Becomes out-of-date:
However, as time passes, and we reach say...2020, logically the 2019 project should have been changed to complete, deferred, cancelled, etc..
Unfortunately though, that rarely happens. Users often fail to change the status of events (despite my reminders for them to check). This results in records where the year was in the past (2019), but the status suggests the event is for the future (proposed). This is logically impossible (an event can't be in the past --and-- simultaneously in the future). So, we have a problem.
Question:
Often in databases, we can prevent wrong data from being entered in the first place (check constraints, no nulls, triggers, etc.). However, in this case, the record was, in fact, correct at the time it was entered, so the aforementioned QC measures aren't applicable.
How can I manage this situation so that users are alerted that their records are out-of-date, as they become out of date?
Note: I'm not an I.T. guy or a developer. I'm just a public works data analyst. This might seem like seem like a silly question with an obvious answer, so feel free to provide negative feedback.
oracle time oracle12c data-integrity data-entry
asked Nov 14 '18 at 21:19
WilsonWilson
10322
add a comment |
I have a construction_events table in an Oracle database. Users enter construction events into the table via GIS software.
For example, a user can enter a construction project for 2019.
The event_status would be entered as proposed.
Starts out as legit:
The record is legitimate at the time that it is entered. The user proposes a project for 2019 which makes logical sense.
Becomes out-of-date:
However, as time passes, and we reach say...2020, logically the 2019 project should have been changed to complete, deferred, cancelled, etc..
Unfortunately though, that rarely happens. Users often fail to change the status of events (despite my reminders for them to check). This results in records where the year was in the past (2019), but the status suggests the event is for the future (proposed). This is logically impossible (an event can't be in the past --and-- simultaneously in the future). So, we have a problem.
Question:
Often in databases, we can prevent wrong data from being entered in the first place (check constraints, no nulls, triggers, etc.). However, in this case, the record was, in fact, correct at the time it was entered, so the aforementioned QC measures aren't applicable.
How can I manage this situation so that users are alerted that their records are out-of-date, as they become out of date?
Note: I'm not an I.T. guy or a developer. I'm just a public works data analyst. This might seem like seem like a silly question with an obvious answer, so feel free to provide negative feedback.
oracle time oracle12c data-integrity data-entry
asked Nov 14 '18 at 21:19
WilsonWilson
10322
3
With a script/job that runs every day, week, whatever that checks this table for inconsistencies and notifies them via email, slack channel, sms message, what-have-you and threatens them with some action of some sort. Darned people.
– JNevill
Nov 14 '18 at 21:29
1
This is a system design question, not really related to programming. This is where you need a business analyst to ask the client what they want to happen when records get "out of date". For example, "there will be a person whose job it is to run a daily report."; or "the system will send an email/sms/robocall to alert a human"; or "the system will simply mark the record as 'expired' after the event date".
– Jeffrey Kemp
Nov 16 '18 at 3:13
@JNevill : Any interest in posting your comment as an answer?
– Wilson
Nov 19 '18 at 23:16
add a comment |
I have a construction_events table in an Oracle database. Users enter construction events into the table via GIS software.
For example, a user can enter a construction project for 2019.
The event_status would be entered as proposed.
Starts out as legit:
The record is legitimate at the time that it is entered. The user proposes a project for 2019 which makes logical sense.
Becomes out-of-date:
However, as time passes, and we reach say...2020, logically the 2019 project should have been changed to complete, deferred, cancelled, etc..
Unfortunately though, that rarely happens. Users often fail to change the status of events (despite my reminders for them to check). This results in records where the year was in the past (2019), but the status suggests the event is for the future (proposed). This is logically impossible (an event can't be in the past --and-- simultaneously in the future). So, we have a problem.
Question:
Often in databases, we can prevent wrong data from being entered in the first place (check constraints, no nulls, triggers, etc.). However, in this case, the record was, in fact, correct at the time it was entered, so the aforementioned QC measures aren't applicable.
How can I manage this situation so that users are alerted that their records are out-of-date, as they become out of date?
Note: I'm not an I.T. guy or a developer. I'm just a public works data analyst. This might seem like seem like a silly question with an obvious answer, so feel free to provide negative feedback.
oracle time oracle12c data-integrity data-entry
asked Nov 14 '18 at 21:19
WilsonWilson
10322
I have a construction_events table in an Oracle database. Users enter construction events into the table via GIS software.
For example, a user can enter a construction project for 2019.
The event_status would be entered as proposed.
Starts out as legit:
The record is legitimate at the time that it is entered. The user proposes a project for 2019 which makes logical sense.
Becomes out-of-date:
However, as time passes, and we reach say...2020, logically the 2019 project should have been changed to complete, deferred, cancelled, etc..
Unfortunately though, that rarely happens. Users often fail to change the status of events (despite my reminders for them to check). This results in records where the year was in the past (2019), but the status suggests the event is for the future (proposed). This is logically impossible (an event can't be in the past --and-- simultaneously in the future). So, we have a problem.
Question:
Often in databases, we can prevent wrong data from being entered in the first place (check constraints, no nulls, triggers, etc.). However, in this case, the record was, in fact, correct at the time it was entered, so the aforementioned QC measures aren't applicable.
How can I manage this situation so that users are alerted that their records are out-of-date, as they become out of date?
Note: I'm not an I.T. guy or a developer. I'm just a public works data analyst. This might seem like seem like a silly question with an obvious answer, so feel free to provide negative feedback.
oracle time oracle12c data-integrity data-entry
oracle time oracle12c data-integrity data-entry
asked Nov 14 '18 at 21:19
WilsonWilson
10322
asked Nov 14 '18 at 21:19
WilsonWilson
10322
edited Nov 15 '18 at 20:46
Wilson
asked Nov 14 '18 at 21:19
WilsonWilson
10322
asked Nov 14 '18 at 21:19
WilsonWilson
10322
asked Nov 14 '18 at 21:19
WilsonWilson
10322
10322
3
With a script/job that runs every day, week, whatever that checks this table for inconsistencies and notifies them via email, slack channel, sms message, what-have-you and threatens them with some action of some sort. Darned people.
– JNevill
Nov 14 '18 at 21:29
1
This is a system design question, not really related to programming. This is where you need a business analyst to ask the client what they want to happen when records get "out of date". For example, "there will be a person whose job it is to run a daily report."; or "the system will send an email/sms/robocall to alert a human"; or "the system will simply mark the record as 'expired' after the event date".
– Jeffrey Kemp
Nov 16 '18 at 3:13
@JNevill : Any interest in posting your comment as an answer?
– Wilson
Nov 19 '18 at 23:16
add a comment |
3
With a script/job that runs every day, week, whatever that checks this table for inconsistencies and notifies them via email, slack channel, sms message, what-have-you and threatens them with some action of some sort. Darned people.
– JNevill
Nov 14 '18 at 21:29
1
This is a system design question, not really related to programming. This is where you need a business analyst to ask the client what they want to happen when records get "out of date". For example, "there will be a person whose job it is to run a daily report."; or "the system will send an email/sms/robocall to alert a human"; or "the system will simply mark the record as 'expired' after the event date".
– Jeffrey Kemp
Nov 16 '18 at 3:13
@JNevill : Any interest in posting your comment as an answer?
– Wilson
Nov 19 '18 at 23:16
3
3
With a script/job that runs every day, week, whatever that checks this table for inconsistencies and notifies them via email, slack channel, sms message, what-have-you and threatens them with some action of some sort. Darned people.
– JNevill
Nov 14 '18 at 21:29
With a script/job that runs every day, week, whatever that checks this table for inconsistencies and notifies them via email, slack channel, sms message, what-have-you and threatens them with some action of some sort. Darned people.
– JNevill
Nov 14 '18 at 21:29
1
1
This is a system design question, not really related to programming. This is where you need a business analyst to ask the client what they want to happen when records get "out of date". For example, "there will be a person whose job it is to run a daily report."; or "the system will send an email/sms/robocall to alert a human"; or "the system will simply mark the record as 'expired' after the event date".
– Jeffrey Kemp
Nov 16 '18 at 3:13
This is a system design question, not really related to programming. This is where you need a business analyst to ask the client what they want to happen when records get "out of date". For example, "there will be a person whose job it is to run a daily report."; or "the system will send an email/sms/robocall to alert a human"; or "the system will simply mark the record as 'expired' after the event date".
– Jeffrey Kemp
Nov 16 '18 at 3:13
@JNevill : Any interest in posting your comment as an answer?
– Wilson
Nov 19 '18 at 23:16
@JNevill : Any interest in posting your comment as an answer?
– Wilson
Nov 19 '18 at 23:16
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53308891%2falert-users-that-their-records-are-out-of-date-as-they-become-out-of-date%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53308891%2falert-users-that-their-records-are-out-of-date-as-they-become-out-of-date%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
3
With a script/job that runs every day, week, whatever that checks this table for inconsistencies and notifies them via email, slack channel, sms message, what-have-you and threatens them with some action of some sort. Darned people.
– JNevill
Nov 14 '18 at 21:29
1
This is a system design question, not really related to programming. This is where you need a business analyst to ask the client what they want to happen when records get "out of date". For example, "there will be a person whose job it is to run a daily report."; or "the system will send an email/sms/robocall to alert a human"; or "the system will simply mark the record as 'expired' after the event date".
– Jeffrey Kemp
Nov 16 '18 at 3:13
@JNevill : Any interest in posting your comment as an answer?
– Wilson
Nov 19 '18 at 23:16