This topic was archived on Mon, 24 Sep 2018 19:28:20 +0000

Archived because: OP requested archive.

Only one standard can be set for a "from" place "to" place.

While setting the standard for the first place clears the flag, both places need to be standardized, not just the "from" place in a move.

1 person likes
this idea
+1
This topic is no longer open for comments or replies.
  • The system is only able to associate a single place with an event. This means that for a move, you should only enter the "to" (new) address as the location. To capture the "from" address, you need a separate Residence entry.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated

  • What I would have done for this entry is have the title "Move From L... to Cook.., the Description: Departure from L...
    Date: when left
    Place L...

    then had a similar event, probably with same title
    Description: Arrival in C...
    Date: when arrived
    Place: C...

    In 1883 those events could have been weeks apart.
    • The problem is that this does not line up with the API for moves from external programs, like Ancestral Quest.

      Yes, I could use the arrival date (and did for the person that this actually applied to), but I was testing to see what the system would do with two place fields and/or two description fields.

      So far, I haven't set up a test for two description fields, but so far, this part needs to be addressed, since the system accepted the two place fields and created the from-to entry you see above.
    • This may be unrelated to the new interface as I did not test this with the old interface, but it is related, then now is the time to fix it.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated

  • As I said to Gordon, the FamilySearch converts a two places entry through its API to the "from Lititz, Lancaster, Pennsylvania, United States to Cook Township, Decatur, Kansas, United States" you see in the screen shot.

    I did this as a test because I have several instances where people moved from one location to another that is documented. Both locations need to be standardized, not just the first location.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated

  • I did an additional test and the "from" - "to" option shows up as part of the standards list, but will not set as a standardized place.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated

  • By the way, the standards can handle the from ... too ... for dates. Since dates are represented by a number, and places are represented by an ID number in the standards, this ability to tag the two places should be able to be done.

    It would be nice if someone from FS would let us know if setting the standard for the two places in "from place1 to place2" is being considered, on the list of thing to implement, or even being developed.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated

  • There are two sides to this: first, there's the parsing of the place name with an attempt to handle both places at once. Second, there's the question of how to handle this type of situation in terms of the user interface and the backend database.

    I can only speak to the first: there are no current plans to support this. Though places are described by unique identifiers (a number), there's no interesting way to combine multiple numbers in such a way as to create a "new" number that represents both. The difference between dates and places is significant enough that the comparison is only superficially interesting.

    In terms of the user interface and the database, something like this is obviously possible, but I can't speak to the priority or plan to do this. As far as I can tell, it's mostly interesting only for the narrow case of a "move" custom event (which is still an interesting event...I've moved many times in my life, so these kinds of events are very relevant).
    • Thanks for the update and information, Dan. I use Ancestral Quest and use its interface through the API to transfer many events, especially move events. Most of the time, I do not include the from or to portion, but in some cases, I do when I know what was involved.

      In fact, I know the exact date my ancestors left the town named after them and crossed over the Oregon Trail. I do not know the date that they arrived and I am continuing to do research in that area -- the answer may even be something that I already know.

      Regardless, Ancestral Quest maintains two place designations -- one for from and one for to. What I do not know is how AQ sends those two place to the API -- if AQ combines the two into one entry "from place1 to place2" or if that is done by the API.

      I no longer do any software development, so I have no interest in exploring the API documentation that exists on FamilySearch. But if the API does the combining, then perhaps in the future, it could be modified to accommodate a "from place" and a "to place" so they could have standards applied to them.

      Thanks again for the response. It pretty much closes any further discussion on this request.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated