Hi Leif,
Sorry you run into these problems: let me give you a little bit of background of how these parameters are working in PersonFinder.
For each application of personfinder deployed in appengine, you can access to an admin page which set all configuration for each instance.
For example, these configurations includes:
- do you require keys to access Read/Write/Search API ?
- how to handle names: do you have firstname/lastname or a single full name.
You can see the different parameters set in:
and
(or if you run a local instance, you go to localhostL8000/admin (make sure to select the admin option when accessing this page).
Recently, Some changes have been made to this config and this is why you saw the change in behavior. Below specific answer to you specific questions:
1) "About the option "This person is believed to be deceased"."
We recently added some support to handle spam because of spam issued we noticed for the Japan Instance.
We added as a configuration option : the option to "I have received information that this person is dead".
So that we can control if in the UI we give that option to people or not (if we see people are abusing it from the UI, we can disable that option).
In the test instance, this option is currently disabled, this is why you do not see it in the UI.
However, through the API, we can allow some API users which we trust to still set this status.
I checked and the key you are using should allow you to still set this status. Let me know of you see any errors with the API?
2) "The form doesn't allow one to enter a first and last name separately"
For each instance, the admin configuration specify if we a firstname/lastname or a fullname.
It seems that the test instance was moved from firstname/lastname to fullname for a couple of days (I think that was just to show to someone and then we forgot to revert it back to firstname/lastname).
I just reverted it back to firstname/lastname and now it should work as before. Sorry about that.
3) "Thirdly, the atom feed lists the name as <first_name> instead of <full_name>."
This is the same issue as 2.
This should be fixed now.
I hope this answer your questions and that your issues are now fixed.
Let me know if you have any other questions,
--