| Author |
Messages |
|
Mark Riley 
Posts:176
 |
| 04/02/2010 10:37 AM |
 Alert
|
Hi Jeff,
Following an import of Locations while trying to rebuild my data base, I now find that I have a duplicate of every location I have ever added. They are at the front of my locations under orphaned locations. The originals are where they should be under there respective parent locations.
When I add a new location it does not duplicate and is where it should be under it's assigned parent. It does not join the orphoned location list.
This is not affecting the running of BD and I am tempted to leave well alone. However this is clearly not how it should be. Any thoughts?
Kind Regards
Mark Riley |
|
|
|
|
SteveO
Posts:509
|
| 04/02/2010 11:48 AM |
Alert
|
If the llocations are where they are supposed to be, and are also under $orphaned location, then they just have an extra parent.
Maybe Jeff knows an easier way, but when I screwed up locations, I did...
Select a location
Cick Edit
In the bottom half of the "Edit" form, select the parent $Orphaned Locations
Click Remove
Click Close
Select a location
Repeat until you get bored.
Do some more the next day |
|
Regards,
Steve |
|
|
jjones
Posts:5105
|
| 04/02/2010 12:21 PM |
Alert
|
Good thinking Steve. I am wondering if these locations are truly doubly-parented (both to where they should be and to the Orphaned location) or if these locations are somehow spelled differently (e.g. an extra space or something).
Editing one of the locations under "$Orphaned Locations$" and checking the list of parents will tell. If they are doubly parented, then follow Steve's advice.
Not sure how you could have gotten here.
Jeff |
|
Birder's Diary Technical Support |
|
|
Mark Riley
Posts:176
|
| 04/02/2010 3:06 PM |
Alert
|
Thanks Steve & Jeff,
Steve your conclusion was what I thought is required
Jeff I have not checked, but how woukd the mis spelling take place? How would importing cause this?
Thanks
Mark |
|
|
|
|
jjones
Posts:5105
|
| 04/02/2010 3:12 PM |
Alert
|
Hi Mark,
My assumption, from your original description, is that you had a location file that you had exported using BD. Then you tried to import it into a new database - or some such thing. If that is all you did, then this should not have happened. But it is all guesswork without knowing all the steps you actually took that got you to this place. And most often, just like me, few folks remember all the steps they took! 
I really have no idea how this could have happened. But, I just exported my county's branch of the location tree and reimported them. No problems, no duplicates and no orphans. So, I don't think it got this way via standard import/export. Let me know if something comes to your mind.
How many of these locations ended up under the orphans?
Jeff |
|
Birder's Diary Technical Support |
|
|
Mark Riley
Posts:176
|
| 04/05/2010 12:56 PM |
Alert
|
Hi Jeff,
Your assumptions are spot on. You may remeber i had to rebuild my database following not being able to open it on a new computer about a year ago. You felt the problem whent back some time. I imported all tha i could etc.
We decided the best way forward was to rebuild. i had not noticed the orphan locations until recently. They appear to be every location i have ever added. Is the best way forward to follow steves advice. It will be a long haul.
Does Steve know how he had the same result?
Regards
Mark |
|
|
|
|
SteveO
Posts:509
|
| 04/05/2010 5:07 PM |
Alert
|
| Not a clue how I did it - but it took me a while to undo it. |
|
Regards,
Steve |
|
|
jjones
Posts:5105
|
| 04/05/2010 9:49 PM |
Alert
|
Hi Mark,
Are your locations under the $Orphaned$ location "doubly-parented"; meaning, do they have more than one parent, one of which is the $Orphaned Locations$ parent and the other(s) are valid parents? Or, is their only parent the $orphan$ parent?
If the former, then edit each and remove the $orphan$ parent. If the latter, just delete then as they are somehow duplicate and not tied to the real location.
Jeff |
|
Birder's Diary Technical Support |
|
|
Mark Riley
Posts:176
|
| 04/06/2010 4:42 PM |
Alert
|
Hi Jeff,
It's the former. It will be a long haul but I'll dio it. Having said that its not causing any new problems.
Regards
Mark |
|
|
|
|
cowboyinbrla
Posts:270
|
| 10/10/2011 10:40 PM |
Alert
|
In a different vein - the same task to do, but for a different reason:
My partner has decided to load his pile of sightings into BD (from the excel spreadsheet he was keeping them in) mostly so I can run him checklists and reports. He uses a different "system" for identifying user-defined locations, so none of his conflict with mine. However, upon import, of course, they're all orphans.
What would be really useful, in situations like this, would be to be able to select one or more locations and drag them to another existing location, which would add them as child locations to that parent. It would make it really easy to drop all the Louisiana locations into Louisiana, all the Mississippi ones into Mississippi, and so forth. I'm sure that's a far-from-trivial feature to implement, but I seem to recall that something vaguely similar exists in the Taxonomy editor for moving things around, so maybe there's a model to build on? |
|
|
|
|
jjones
Posts:5105
|
| 10/11/2011 9:17 AM |
Alert
|
Hi Kevin,
I agree, the currently functionality is not very multi-location friendly. 
Very non-trivial. As the default MS tree component does not support multi-selection; and the code written to allow that in the Tax Viewer cannot easily be reused. (I will have to have a talk with the developer on that one.  )
In my mind, I would tackle this differently with a new dialog that allowed for specifying multiple locations to re-parent.
I will enter a wishlist for this.
Jeff |
|
Birder's Diary Technical Support |
|
|
|