2 topics here - 1 about what Rangers do & 1 about profile policy/style

+12 votes
473 views

One of the things Rangers do is to offer assistance when we see something being done in a profile that could (or should) be done better or differently.

I recently saw that someone had done a beautiful job of cleaning up the biography after a merge, except for one thing.  The sources section started with the ones that were not footnoted and, under them, there was another section named "Footnotes" where these were displayed.

I left a comment on the profile of the person who had done that, complimenting him/her for the good work done and suggesting how the style guide specifies that sources should be listed.

He/she promptly responded by sending me a private message.  I think the well thought out message raises some excellent points and wish that he/she had posted that as a G2G question to open up a discussion here about his/her points ... so... I decided to quote the private message here (removing anything that might identify the sender):

I think the guidelines you mention are great for adding sources to a profile.  They are easy to understand and will help to encourage more people to add sources.  However, the current guidelines don't address the methods WikiTree uses when importing your family tree.  It also doesn't address the problems caused by merging profiles, and how to fix them.  These are more difficult problems, that will not be understood by most people on WikiTree.  The technical description of how WikiTree builds profiles with sources and footnotes are described here:  http://www.wikitree.com/g2g/146810/technical-discussion-about-wikitree-syntax-and-footnotes.  I think you will agree that most people will not be able to understand this description.  This is probably the main reason more people are not cleaning up their profiles.  On the other hand, I have seen people clean up their profiles by simply deleting sources or deleting source information.  Sometimes I think they are deleting source information so that they can better conform to the guidelines you mention.  This certainly makes it easier, but it is definitely not the intention of the guidelines. The solution you are suggesting (described in the guidelines) is possible, but this introduces another problem:?  bloat.  This problem is described here:  http://www.wikitree.com/g2g/145135/editing-porofiles-that-use-inline-references-for-sources.  With a small profile, with just a few sources, this is a minor problem that can be ignored.  With a large profile, and many sources, this is a very big problem.  When a profile has been created from multiple GEDCOMs/mergers, bloat becomes such a big problem that most people will not attempt to clean up the mess.  I think the only long-term solution is to stick with the method WikiTree has always used, and continues to use when importing a family tree.  This uses a separate source section for source information (span id) and reference tags.  This allows us to reduce the size footnotes (bloat) and make it easier to manage a large amount of information in a profile.  I hope the guidelines can be expanded someday, to include both this method and easier methods of adding footnotes.  I've struggled with creating a description of how to clean up messy profiles, but it is just too complicated (although I haven't given up).

in Policy and Style by Gaile Connolly G2G Astronaut (1.2m points)
edited by Keith Hathaway

4 Answers

+6 votes
Gaile, Part of the problem is when a new profile is created the system only partialy follows the style guide.  For example it leaves out the See also: line that is recommended.  The other part of the Style problem is that there are so many older profiles that use <span> and not<ref> so that when merging a newer user may not understand that the only recommended "fotnote" tag is <ref>.  The only solution is to have the profiles edited only using WikiTree recommended codes, and with the very large number of profiles on here that gonna take a little time.  But I try to "fix" at least a couple each day.
by Dale Byers G2G Astronaut (1.7m points)
I will just stay out of it.
Beautiful!!!   I just made a little change - I didn't like that all the numbers were in a column, 1 below the other, so I changed the spacing.  I removed the blank lines but still tried to keep space between the different sources by using the <ref> and </ref> tags to separate them.  Please see what you think.

Now, how about making a new G2G post with your incredible idea as a formal proposal of a replacement to the current style guide source instructions?

By the way, this can also go iinto new profiles created by gedcom to give people an example that makes it easy for them to start using it.
Gaile I will let you propose it as I am going to be very busy with other things for the next few days, or weeks even.  Not to mention that my fingers and eyes hurt from all of the typing today.
Chryse,

I think everyone in on this has agreed that the "1 2 3" stuff on the view page is less hideous than the confusing mess on the editing page the way we now do it.

If you comment it out then it will be as if it were not there to begin with, so that won't solve anything.  As I set out above, there is a very easy and effective way to hide it, but it would take a very minor programming change to do it.  I am hoping that we can persuade Chris to do this.

By the way, when you want to wrap something in a comment tag set, it starts with <!-- and ends with -->.
OK Dale - I'll try not to embarrass you too much, but brace yourself for an outpouring of accolades from all of WikiTree.  I'm not sure you fully appreciate how truly amazing your system is.
I had a professor in college for one of my computer courses who told the whole class that I "think like a CPU"
Edited out
That was one sharp professor, who recognized greatness when he saw it, Dale!!!
I added a new profile earlier today when I found one more child for a couple that they did not have on their profiles - was found in the source I looked up because it was mentioned in a public comment - now I noticed that the style was wrong as soon as I saved and looked back at the Profile and I had to move and delete and move stuff so it looked standard - I think sometimes we just need to take time and look and see if it is ok, not rush off to another profile to fix or back to where we were before we found a source for this one - if we are going to do it let's do it right
+4 votes
Edited out
by Anonymous Whitis G2G6 Mach 2 (21.5k points)
edited by Anonymous Whitis
Chryse, thank you for your answer.  The problem is not really the GEDCOM inport but rather editing the profile to fit our style guide.  The method recomended by the Style guide is

Dale was born in 1951 to Father and Mother <ref>place source information here</ref>

This creates a lot of source text mixed in with the narrative and that makes editing harder later on.

(Makes editing harder later on to some.)

devil

Edited out
+3 votes
Edited out
by Anonymous Whitis G2G6 Mach 2 (21.5k points)
edited by Anonymous Whitis
+3 votes
Two side to everything (except where there are three or four or five sides)...

So when I started at WikiTree, I learned the advanced source style, as described on the help page.

Then, there were comments that it was too difficult to see which comment the source applied to, when it could be part of a 1.1, 1.2, 1.3 etc string.

So I started using the simple style which assigns a number to each reference. I include the vol and page number for each reference in the footnote.

Now we are full circle, back to preferring the advanced style.

I have no objection to either style, however have found the simple style easier to read and understand in the published mode. Yes, it is more difficult to read in the edit mode. Which is better for visitors and for printouts?
by April Dauenhauer G2G6 Pilot (125k points)
I have found the same thing.  What is the problem with the old way of using [[Source XXX]] at the bottom and <ref>[[Source XXX]] Vol. x, Page y. </ref> in the text.   Or, with the other way of putting the full cite in the first use, <ref> Author, Title, etc.</ref> and an abbreviated cite <ref> Author, Vol. X, Page y</ref> for the next use.  Both make nice, clean cites at the bottom.
Hi April,

Your question about which is better for visitors and printouts might as well be rhetorical - anybody, visitor or logged in member, who is looking at a profile is ONLY looking at the view page, so of course we want that to look the very best it can.

The problem is that all profiles on WikiTree are - and are destined to always be - works in progress, so it is also important that the editing page be easy to use because of our dedication to collaboration here.

When the inline sources (all the <ref> ... </ref> tags) contain long citations, often including URLs that have lots of parameters that are frequently written using entities and character callouts instead of just plain text, it severely impedes the ability to read the narrative easily.

This often leads to people who try to add more information to the narrative ending up accidentally fouling up the source citations or the narrative itself.  Sometimes it also leads to people being so confused that they give up, or more likely in the case of newer members, being afraid to even try to make a contribution.

So .... even though the answer to your question is a no-brainer, there is a very solid case for needing editing capability to be easily accessible to all members.  The result is that we may have to accept a trivial underachievement on the view page in order to provide a major improvement to the editing interface.

OK - aafter that long-winded argument in favor of the new system, I really don't think that old vs new is the issue you are concerned with.  This new approach doesn't create the 1.0, 1.1, 1.2, etc. string, although it does exacerbate it a little, since every source will have at least 2 tags - the first where it is used in the narrative and the second where all the numbers only are listed just under the Sources heading.  The decision of whether to use the full citation each time a source is footnoted (what you called "simple") or to use the empty tag (<ref name="something" /> for multiple footnotes using the same source (what you called "advanced") is not at all affected here.  You can still do it either way.

Now, to complete the full circle you mentioned, I'll comment on the start of your answer ... I hope this isn't adding another side ... that would be putting the "hex" on your pentagon.
LOL Gaille. I like your post very much, and realize I didn't read the original posts carefully - I can see this might be a very good solution to "conplex vs readable" conundrum.

Okay, I must agree that Dale's solution is elegant and brilliant. I will make the attempt to use it.

PS sorry for the rhetorical question - I hate those:)
April, you are the greatest!  I was ready to duck when the rotten tomatoes started heading my way in response to my last line!!!  I know I'm bad, but even I thought I might have gone too far with that one.

There is an easy solution to the string of numbers that get added with this new style (they will appear immediately under the Sources heading before the numbered list displaying all the citations.  In fact, there are 2 possible solutions (one that I thought of and one that Rob Ton recommended) and they're both easy.

If everyone decided that the 1.0, 1.1, 1.2, ... business is undesirable then there is an easy solution to that, also.

Both of these fixes would require WikiTree to make some modifications, though.
Thank you for summing up the solutions, Gaille - I will find them now.

Nah, no rottoen tomatoes - you are funny and we have the same sense of humor:)

Related questions

+15 votes
1 answer
440 views asked Nov 9, 2014 in Policy and Style by Anne B G2G Astronaut (1.3m points)
+58 votes
9 answers
+10 votes
1 answer
+9 votes
2 answers
+43 votes
20 answers
+7 votes
4 answers
561 views asked Feb 4, 2023 in Policy and Style by Jimmy Honey G2G6 Pilot (163k points)
+6 votes
2 answers
255 views asked Aug 8, 2023 in Policy and Style by Christy Gregg G2G2 (2.2k points)
+7 votes
2 answers
+41 votes
16 answers

WikiTree  ~  About  ~  Help Help  ~  Search Person Search  ~  Surname:

disclaimer - terms - copyright

...