Consistency checker doesn't seem to understand negative numbers - dates BC. See for example Julius Caesar, Roman Dictator
Thanks all, I'll work on fixing those date issues.
Leanne, there would be some limitations with adding that as an option. It would only work in profile view and only the profile you're viewing. That's because it's not available via the API, so it would just be looking at the page code and seeing that it's in the menu, then making an alert based on that. Would that still be useful?
On the incomplete dates, such as "Jan 20"... I've wrote something to handle this, but as an FYI it will assume that format is a day. So if you just have a Month and Numeric, years 1-31 will be considered days of the month and not years. So Jan 20 is January 20th, not January 20AD. If it's just the year or if it's day month and year, it will be uneffected, but if it's just a month and year, years 1AD through 31AD will not work.
Private User it's expensive to generate, so you have to ask for it specifically.
https://www.geni.com/api/profile?fields=name,data_conflict
Private User, double check this profile:
Private
When running smartcopy consistency checker it gives an error saying that the birth date is after the death date. When looking to the profile I found that the date is wrongly included as no month has been included.
I suggest to include the following logic:
- Give a warning on the profile having this case, no month but the day of a date is included. Whatever the date of the profile.
- When checking, include an specific warning for this profile and maybe only use the date as "circa".
I'm looking at rewritting a good bit of code on how I query this, not only for the date thing but also Erica's request. I do some things on the backend, which I had written for the purpose of SmartCopy copying, but which don't work well for consistency checking. For example, on the back end I change the date to a single field, which makes it easy for viewing when doing the side by side comparison. But in doing so, I lose the ability of fields for day, month, year. This make take a little time to work out as I have to rewrite the code that processes Geni's return.
Still some trouble with date parsing in 4.0.4.
The checker flags this guy as being > 125 years:
https://www.geni.com/profile/edit_basics/6000000046562214900
His birth is 8/1961 and his death is 10/2002.
Harald Tveit Alvestrand, that should be resolved in the next version, but that is one that it's going to give an info warning on because the 8 is actually a day, not a month. Geni might have a bug here. Mike Stangel, the edit screen shows "August, 1961" for Sven Georg Axelsen but the API is actually returning the day as 8 with no month. {day: 8, year: 1961, formatted_date: "8, 1961"}
Should I be treat it differently assuming it's a month in these instances where there is a day but no month?
re: days less than 13.
Ambiguous data. If the original text string was unambigous (e.g. Aug 1961), then it can (&should) be assigned as month=8. If original text was something such as "8/1961" ... that's ambiguous and the best that can be done is to be consistent about the interpretation (on both input and outputs).