User talk:Dallan

Old topics archived: 2007, 2008, 2009, 2010, 2011, 2012, 2013-16

Topics


does the server need a reboot? [1 January 2017]

Just wondering. The site is VERY slow today. Slow enough to make one want to click out and leave. We sure don't want that on a weekend holiday! --janiejac 02:02, 1 January 2017 (UTC)

I just rebooted it. I hope it helps. Happy new year!--Dallan 06:24, 1 January 2017 (UTC)

GEDOM stuck in system [18 March 2017]

Hi Dallan, I'm copying this email exchange from the watercooler page:

I must have been wrong when I assumed I had rights to get my GEDCOM accepted w/o admin review. It was always accepted so quickly before but today it is taking a long time. I uploaded it at 2:20 this afternoon and still is not accepted so that I can review it. I realize we're short handed or maybe my status has changed??? --janiejac 22:05, 16 March 2017 (UTC)

It looks like it may be stuck on Waiting for analysis. Normally I can review GEDCOMs just fine, but it's currently in a state where I can't do anything. It may need to be re-uploaded, but I'm really not sure.--khaentlahn 22:11, 16 March 2017 (UTC)
Janiejac - your admin rights have not changed. I put a request in to Dallan to take a look at that file, so hopefully we'll have an answer soon. He is still the go-to person for files that are stuck in the automated part of the process. In the meantime, can you re-create your GEDCOM under a new name name and try uploading again. If the 2nd version processes normally, please proceed with that one, and leave the 1st version as is. If the 2nd version gets stuck as well, please contact either Dallan or me and we'll go from there. Thanks, --cos1776 11:46, 17 March 2017 (UTC)
The system won't let me upload a renamed GEDCOM. Can you get it unstuck?? I get this msg:
You have a GEDCOM already in process
Before importing a new GEDCOM you need to wait for your earlier GEDCOM to finish importing --janiejac 23:22, 17 March 2017 (UTC)

The server that processes GEDCOMs crashed. It's up again now and the GEDCOMs that were waiting are ready for user review.--Dallan 06:35, 18 March 2017 (UTC)


GEDCOM stuck again?? [26 March 2017]

It is quite frustrating to hang around waiting for the GEDCOM to be accepted. I wonder how many folks just leave and don't bother to come back??? Very small GEDCOM uploaded abt 1 o'clock; and it doesn't need admin review. So is it stuck again? --janiejac 18:01, 26 March 2017 (UTC)


Jammed up again [22 May 2017]

I think someone has left the GEDCOM review machine unplugged again, Dallan. There's a couple of us have been hanging fire there all morning, "waiting for analysis." --MikeTalk 16:49, 8 May 2017 (UTC)

Follow up: As of this morning, there are 3 still in limbo. I would guess it is a server reboot issue again. I've sent Dallan an email (often works better for reaching him now). Hopefully it will be resolved soon. Thanks for your patience. --cos1776 15:34, 9 May 2017 (UTC)
And now there are four. And it's been four eight days. Something really needs to be done about this. --MikeTalk 18:22, 12 May 2017 (UTC)
Finally fixed it.--Dallan 02:22, 23 May 2017 (UTC)

Want to tidy up a mis-spelling [17 May 2017]

Hi Dallan I was just having a look at New Brunswick, Canada and noticed we have two spellings for Westmorland County with a number of settlaments within both. Would you be kind enough to redirect [[Place:Westmoreland, New Brunswick, Canada|Westmoreland]] to [[Place:Westmorland, New Brunswick, Canada|Westmorland]]. Without the "e" is correct.

Many thanks, --Goldenoldie 14:30, 17 May 2017 (UTC)

All done. --khaentlahn 15:33, 17 May 2017 (UTC)

Thanks

--Goldenoldie 15:57, 17 May 2017 (UTC)


Quebec--I mean Québec [20 July 2017]

Hi Dallan

The "WeRelate agent" has just added some acute accents to "Quebec" for me. These are in tiny townships which I added in bulk a day or two ago with the intention of coming back and making a better job of a descriptive paragraph and adding links that change from place to place.

Earlier, reading through the proposed alterations we are thinking about making, I wondered if this little problem could be solved in some automatic fashion. At the moment, although I have been told what the code for an acute accent is, I can't figure out how to put it in the text without copying and pasting--an action it is easy enough to forget to do. Ordinary users adding their own French-Canadian ancestors may have little knowledge of French and may not realize that small places (and defunct places) in Quebec all have to have "Québec" in the placename. I am picking up numerous examples with redirects, but I'm not sure I will remember to check "What links here" for every hamlet and township.

Yes, I am trying to sort out Québec, going on from where Jennifer left off a few years ago. Many of the URLs for reference websites have changed over time and Jennifer and I don't have quite the same principles of how to set up a page, so it is slow work. My knowledge of Québec geography is not as great as you might think. I have been very surprised how much schoolgirl French I do remember from 60 years ago. Google Translate is a wonderful tool.

Regards Pat----Goldenoldie 16:03, 19 July 2017 (UTC)

An automated solution could be implemented. What do you think? How about something that checked if you were trying to add a place ending in "Quebec, Canada" and if so, automatically changed the ending to Québec, Canada?
Yes. That's exactly what I was getting at. Off the top of my head I don't know of any other places where we are providing potholes for people to fall into, but that is not to say they don't exist.
Just remembered. Us foreigners don't always know how to spell Massachusetts and Conneticutt/Connecticut?? (aarrrghh!).

/cheers, Pat----Goldenoldie 19:04, 19 July 2017 (UTC)

Hi Pat. CONNECT I CUT is how I remembered in 4th grade. For Massachusetts, you're on your own. --SkippyG 20:13, 19 July 2017 (UTC)
Hi Pat! During GEDCOM upload, places are matched to the database, so they would be entered and linked correctly (with appropriate accents). Likewise, during manual entry, users can select from the dropdown menu, so places are entered correctly. I'm not sure I understand when this might be a problem? Can you clarify a little more? When do you foresee that users might enter Québec without the accent? There are old occurrences of that, but they are slowly being corrected. Thanks, --cos1776 20:25, 19 July 2017 (UTC)

This conversation just shows how many people have put their own family history notes into a mechanical gedcom and uploaded them to WeRelate. Adjusting red-linked places or just investigating "Who links here" for a place leads to finding all sorts of ways of referring to Québec. Just look at the possibilities listed in "Also known as" under [[Place:Québec, Canada|Québec, Canada]]. I have redirected all the possibilities listed so that they will all be picked up if a user just gives the province, but if a user writes St. Joseph de Beauce, Beauce, Quebec, Canada instead of Saint-Joseph-de-Beauce, Beauce, Québec, Canada the place may end up being red-linked. In WeRelate's presentation we see only what is after the pipe; the adjustment that precedes the pipe is invisible until you click "Edit" or aim your cursor at the place on the page. That is not going to make people aware that Quebec is really Québec.

Currently I am trying to improve our provision of descriptions of places in Québec and, as I explained to Dallan, even I can go wrong repeatedly if I don't get my cut-and-paste right.

/cheers, Pat----Goldenoldie 06:02, 20 July 2017 (UTC)


GEDCOM Export Ready [19 September 2017]

The GEDCOM for tree Billings is ready to download. Click here.


GEDCOM Export Ready [19 September 2017]

The GEDCOM for tree Stephenson is ready to download. Click here.


GEDCOM Export Ready [19 September 2017]

The GEDCOM for tree Wells is ready to download. Click here.


server need a reboot?? [8 October 2017]

I can't get any results using the search button on top menu. I even went to Home Page and did a search. Nothing...the little circle just keeps going round and round. --janiejac 19:49, 8 October 2017 (UTC)


Page of the Week [8 January 2018]

If you need a featured page of the week, I would be honored to have my Abraham Ross page featured.

Thanks, Pam Pollard Txbluebell6--Txbluebell6 15:55, 8 January 2018 (UTC)


Wales and the United Kingdom [22 January 2018]

Hi Dallan

In June of 2016 we had a long discussion on places and the use of the suggestion box which comes up when a user starts to type something into a place box. At the time you were trying out a revision of the way the hints were provided.

There was never any problem until I got back to tackling Wales a month or two ago. WR policy is to despense with the words "United Kingdom" following the county (England, Scotland, Northern Ireland and Wales). This applies to whatever time period we are working with. But all place hints for Wales end in "United Kingdom". Trying to avoid "United Kingdom" often ends up in getting a long phrase with a "|" in the middle when only the first part is needed.

This list on [[Place:Wales|Wales]] may have something to do with it.

Also located in United Kingdom(1927 - )
See alsoKingdom of England1542-1649
Kingdom of England1660-1707
Kingdom of Great Britain1707-1800
United Kingdom of Great Britain and Ireland1801-1927

Wales, Yorkshire, England could be changed to [[Place:Wales (parish), Yorkshire, England|Wales (parish), Yorkshire, England]]. This has been my solution to naming the "principal areas" of Wales that came into being in 1996 and that may or may not have the same names as towns that existed earlier.

It would be appreciated if you could have a look at this problem--it would speed things up no end.--Goldenoldie 12:22, 9 January 2018 (UTC)


Somehow the table that I use for auto-completing places seems to have gotten messed up around the UK. It should include names ending in Wales, but not ending in Wales, United Kingdom as was discussed. I just re-loaded it from scratch. It looks better now to me. Would you please let me know if you see any other problems? Thank you!--Dallan 21:31, 15 January 2018 (UTC)


It's been a busy day and I have just got around to looking at the Wales, United Kingdom problem. Hurray, I can now be lazy and click down rather than writing "----shire, Wales" in full. Hopefully, other users will find this helpful too.

Hate to tell you, but in the meantime I have discovered another frustrating quirk. I found the link to the "MediaWiki:Place types" page and added "Community (Wales)". This is the description of the smallest unit of local administration as divised by the Welsh in 1974 and in country-wide use since that date. Users wanting to know what it means will find a definition in Wikipedia.

Trouble is: in saving the page with the new description, the upper case "W" is automatically converted to lower case and then the saving-page mechanism refuses to recognize it as an acceptable type of place. So I go back, change the lower-case "w" that is now there to upper case, save the page again, and guess what? ---- Since I am only willing to go round in circles twice, I end up calling the place a "community", a definition that could mean anything anyone might want to think of.

I hope this is a simple correction too.

regards, Pat--Goldenoldie 19:24, 16 January 2018 (UTC)

I was curious what you were up to with that. Perhaps "Community" should only be used for Wales. Elsewhere a community would more properly be described as an "Inhabited place". It would be nice if the place types could have associated descriptions that wouldn't be a part of the type name which would then give users an idea of how the type is used. Then you could give the Community a description like "Welsh unit of government". -Moverton 20:51, 16 January 2018 (UTC)

I agree, but this needs re-creating the type descriptions as a table. The first column would be used as currently; the second for guidance. The table would be simple, but the software to go with it would call for someone with know-how. --Goldenoldie 07:58, 17 January 2018 (UTC)


I'm not sure why it lower-cases the W. I'll look into this on Sunday.--Dallan 13:56, 18 January 2018 (UTC)

This should be fixed now.--Dallan 15:33, 22 January 2018 (UTC)