|
| Follow-ups |
Submitted By: Andrew Tolopko
Adddate: 2008-10-02 13:11:06
Caroline, Su, and Katrina:
Did I capture the below request correctly? I'm now questioning whether
I did. If so, just curious why this ID expiration field is more
significant than other fields and requires administrative tracking?
thx!
@
> [ant4 - Tue Jul 22 15:45:06 2008]:
>
> Changes to a user's "Harvard ID Initial Expiration" field should
be
> tracked with an administrative activity, capturing who and when the
> change was made.
> |
Submitted By: Andrew Tolopko
Adddate: 2008-10-02 13:11:06
Andrew,
It is somewhat an obscure reason, but a very real one. This date can be
entered by a different staff member depending on how the user gets an ID. If I
request a temp ID, than I can put in the requested expiration date that I give
or if they have a real ID but the # and date are entered at a separate time
than it would be nice to know who it was entered by.
I hope this gives you some idea of why it would be helpful for us. Thanks!
Katrina
-----Original Message-----
From: Andrew N Tolopko via RT [mailto:reply@rt.med.harvard.edu]
Sent: Tuesday, July 22, 2008 3:48 PM
To: Shamu, Caroline Elizabeth; Rudnicki, Katrina L.; Chiang, S. L.
Subject: [HMS #151946] add admin activity for user's havard id initial
expiration field
Caroline, Su, and Katrina:
Did I capture the below request correctly? I'm now questioning whether
I did. If so, just curious why this ID expiration field is more
significant than other fields and requires administrative tracking?
thx!
@
> [ant4 - Tue Jul 22 15:45:06 2008]:
>
> Changes to a user's "Harvard ID Initial Expiration" field should
be
> tracked with an administrative activity, capturing who and when the
> change was made.
>
|
Submitted By: Andrew Tolopko
Adddate: 2008-10-02 13:11:07
Perhaps we should have separate fields for "requested" and
"actual" ID
expiration dates?
If we did, would that obviate the need for the "entered by &
date"
info on the existing ID expiration date field?
As an aside, it seems we really need a full audit log of *all* edits
that are made to all fields of users, screens, etc. I would much
prefer to address this is a system-wide feature rather than sprinkling
"entered by & date" fields throughout the data model and user
interface. It gets a little messy, aesthetically and conceptually.
Is this something you could wait for? In particular if I added the
requested/actual expiration date?
Of course, if you absolutely want the "entered by & date", I'll
do it! :)
@
On Tue, Jul 22, 2008 at 4:04 PM, Katrina L. Rudnicki via RT
<reply@rt.med.harvard.edu> wrote:
> ID: 151946
> Subject: RE: [HMS #151946] add admin activity for user's havard
id initial expiration field
> Status: open
> Owner: Andrew N Tolopko [ant4]
>
> Requestors: caroline_shamu@hms.harvard.edu,
katrina_rudnicki@hms.harvard.edu, su_chiang@hms.harvard.edu
> Cc: (none)
> Queue: Screensaver
>
> Ticket URL:
https://rt.med.harvard.edu/Ticket/Display.html?id=151946
>
> Comment & Take: mailto:take-151946@rt.med.harvard.edu
> Reply & Resolve: mailto:resolve-151946@rt.med.harvard.edu
>
> This is correspondence. It is sent to all ticket watchers.
> -------------------------------------------------------------------------
> Andrew,
>
>
>
> It is somewhat an obscure reason, but a very real one. This date can be
entered by a different staff member depending on how the user gets an ID. If I
request a temp ID, than I can put in the requested expiration date that I give
or if they have a real ID but the # and date are entered at a separate time
than it would be nice to know who it was entered by.
>
>
>
> I hope this gives you some idea of why it would be helpful for us.
Thanks!
>
>
>
> Katrina
>
>
>
> -----Original Message-----
>
> From: Andrew N Tolopko via RT [mailto:reply@rt.med.harvard.edu]
>
> Sent: Tuesday, July 22, 2008 3:48 PM
>
> To: Shamu, Caroline Elizabeth; Rudnicki, Katrina L.; Chiang, S. L.
>
> Subject: [HMS #151946] add admin activity for user's havard id initial
expiration field
>
>
>
> Caroline, Su, and Katrina:
>
>
>
> Did I capture the below request correctly? I'm now questioning whether
>
> I did. If so, just curious why this ID expiration field is more
>
> significant than other fields and requires administrative tracking?
>
>
>
> thx!
>
> @
>
>
>
>> [ant4 - Tue Jul 22 15:45:06 2008]:
>
>>
>
>> Changes to a user's "Harvard ID Initial Expiration" field
should be
>
>> tracked with an administrative activity, capturing who and when the
>
>> change was made.
>
>>
>
>
>
>
>
> |
Submitted By: Andrew Tolopko
Adddate: 2008-10-02 13:11:08
This option sounds good Andrew--two diff fields--a requested exp date and an
actual exp date.
Then there is no need for the entered by date and fields.
Thanks!
-CES
-----Original Message-----
From: Andrew N Tolopko via RT [mailto:reply@rt.med.harvard.edu]
Sent: Wed 7/23/2008 6:28 AM
To: Shamu, Caroline Elizabeth; Rudnicki, Katrina L.; Chiang, S. L.
Cc:
Subject: Re: [HMS #151946] add admin activity for user's havard id initial
expiration field
Perhaps we should have separate fields for "requested" and
"actual" ID
expiration dates?
If we did, would that obviate the need for the "entered by &
date"
info on the existing ID expiration date field?
As an aside, it seems we really need a full audit log of *all* edits
that are made to all fields of users, screens, etc. I would much
prefer to address this is a system-wide feature rather than sprinkling
"entered by & date" fields throughout the data model and user
interface. It gets a little messy, aesthetically and conceptually.
Is this something you could wait for? In particular if I added the
requested/actual expiration date?
Of course, if you absolutely want the "entered by & date", I'll
do it! :)
@
On Tue, Jul 22, 2008 at 4:04 PM, Katrina L. Rudnicki via RT
<reply@rt.med.harvard.edu> wrote:
> ID: 151946
> Subject: RE: [HMS #151946] add admin activity for user's havard
id initial expiration field
> Status: open
> Owner: Andrew N Tolopko [ant4]
>
> Requestors: caroline_shamu@hms.harvard.edu,
katrina_rudnicki@hms.harvard.edu, su_chiang@hms.harvard.edu
> Cc: (none)
> Queue: Screensaver
>
> Ticket URL:
https://rt.med.harvard.edu/Ticket/Display.html?id=151946
>
> Comment & Take: mailto:take-151946@rt.med.harvard.edu
> Reply & Resolve: mailto:resolve-151946@rt.med.harvard.edu
>
> This is correspondence. It is sent to all ticket watchers.
> -------------------------------------------------------------------------
> Andrew,
>
>
>
> It is somewhat an obscure reason, but a very real one. This date can be
entered by a different staff member depending on how the user gets an ID. If I
request a temp ID, than I can put in the requested expiration date that I give
or if they have a real ID but the # and date are entered at a separate time
than it would be nice to know who it was entered by.
>
>
>
> I hope this gives you some idea of why it would be helpful for us.
Thanks!
>
>
>
> Katrina
>
>
>
> -----Original Message-----
>
> From: Andrew N Tolopko via RT [mailto:reply@rt.med.harvard.edu]
>
> Sent: Tuesday, July 22, 2008 3:48 PM
>
> To: Shamu, Caroline Elizabeth; Rudnicki, Katrina L.; Chiang, S. L.
>
> Subject: [HMS #151946] add admin activity for user's havard id initial
expiration field
>
>
>
> Caroline, Su, and Katrina:
>
>
>
> Did I capture the below request correctly? I'm now questioning whether
>
> I did. If so, just curious why this ID expiration field is more
>
> significant than other fields and requires administrative tracking?
>
>
>
> thx!
>
> @
>
>
>
>> [ant4 - Tue Jul 22 15:45:06 2008]:
>
>>
>
>> Changes to a user's "Harvard ID Initial Expiration" field
should be
>
>> tracked with an administrative activity, capturing who and when the
>
>> change was made.
>
>>
>
>
>
>
>
>
|
Submitted By: Andrew Tolopko
Adddate: 2008-10-23 18:17:02
The discussion about adding "entered by" and "entered date"
info is obsolete; off-line discussions revealed that this info was only
necessary if using a single field for expiration date: admins thought they
might have to track down who entered the info in order to ask whether it was
"requested" or "actual"! |
|
|