[jira] [Commented] (INFRA-12008) Correcting LDAP createTimestamp for pre-200905 accounts

["Sebb (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/INFRA-12008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15311321#comment-15311321 ] 

Sebb commented on INFRA-12008:
------------------------------

Is it worth the effort of updating LDAP?

Why not just create an override file for the incorrect dates?
So long as Whimsy has the data, does it matter where it comes from?

Note: AFAICT createTimestamp is like modifyTimestamp, i.e. it is maintained by LDAP itself. This is why it is not visible by default.

> Correcting LDAP createTimestamp for pre-200905 accounts
> -------------------------------------------------------
>
>                 Key: INFRA-12008
>                 URL: https://issues.apache.org/jira/browse/INFRA-12008
>             Project: Infrastructure
>          Issue Type: Task
>          Components: LDAP
>            Reporter: Nick Burch
>            Priority: Minor
>         Attachments: dates.ldif
>
>
> Currently, the earliest {{createTimestamp}} in LDAP is 20090519, which corresponds with when the full LDAP import happened. This is problematic for things like the {{projects.a.o}} timeline + {{accounts-evolution.json}} data, and for the ComDev locations map over time.
> Using the {{[NOTICE] Account created}} messages from the private mail archives, it is possible to work out creation dates for many accounts, and set an earlier dummy date for the very old ones.
> The attached ldif modify file will set actual creation dates for accounts created between early July 2004 and 19th May 2009 (earliest "valid" date currently), and set all pre-existing ones to the 1st July 2004 (to give a slightly more accurate default)
> Could you please sanity check this, then apply with ldapmodify?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)