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

Sebb commented on WHIMSY-63:
----------------------------

Doesn't look like it.

The overides are in the file
https://gitbox.apache.org/repos/asf?p=whimsy.git;a=blob;f=lib/whimsy/asf/person/override-dates.rb;hb=HEAD

and the data is applied in ASF::Person::createTimestamp():
https://gitbox.apache.org/repos/asf?p=whimsy.git;a=blob;f=lib/whimsy/asf/person.rb;hb=HEAD#l89

However there does not seem to be a JSON file that includes the createTimestamp.

At present public_ldap_people.json only includes:
- id
- name
- URLs
- fingerprints
- noLogin

Is there a need for the overrides to be available separately?

It might make sense to add createTimestamp to the existing output.

> Provide a feed of account creation dates with corrected data
> ------------------------------------------------------------
>
>                 Key: WHIMSY-63
>                 URL: https://issues.apache.org/jira/browse/WHIMSY-63
>             Project: Whimsy
>          Issue Type: New Feature
>          Components: PublicData
>            Reporter: Nick Burch
>         Attachments: override-dates.json
>
>
> As discussed on INFRA-12008, 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. 
> As Infra feel that maintaining the corrected creation date in LDAP isn't a 
> core need, and it would be very painful to fix the current data, we should 
> instead have Whimsy publish a fixed list. This would read the 
> {{createTimestamp}} from ldap, and apply a correction for most (but not all) 
> 2004-2009 accounts based on account creation notices. (We can potentially 
> extend it later for pre-2004 accounts too)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to