Adrian Bruce's Data Model Workspace - Evidence and Conclusions
Executive Summary
- Elizabeth Shown Mills refers to a process of Analysis that has input Evidence and output Conclusions;
- The “evidence and conclusion” mode of working enables the permanent and separate recording of the input Evidence to an Analysis, and output Conclusions from that Analysis;
- The “evidence and conclusion” mode of working is entirely optional in the BetterGEDCOM data model;
- In the “evidence and conclusion” mode of working, we propose that input Evidence and outputs Conclusions are recorded on separate Person records;
- If a person record is used as input to an Analysis, it is referred to as an “Evidence Person”;
- If a person record is used to record output from an Analysis, it is referred to as a “Conclusion Person”;
- A “Conclusion Person” can then be used as an input to the next Analysis and from then on is therefore both a “Conclusion Person” and an “Evidence Person”;
- When repeated Analyses give rise to a chain or tree of Person stacked on Person, the current working hypothesis is the Person at the top of the chain.
In detail
The vast majority of family historians hold one record in their data files per person. As new sources come in, we mentally select data from those sources, analyse it, and if we conclude that the new information belongs to one of our existing people, we enter the details of the source into a new Source record, add the new information to our existing person, and, if we’re good, enter a citation and we also record some notes about our analysis somewhere.
The records for this person on our file therefore contain all the current conclusions for this person. Hence we can refer to this as a “conclusion person”. But don’t get hung up on the finality of the word “conclusion” – it’s really a “current working hypothesis” for the person that we have in our files. But Elizabeth Shown Mills uses the term “conclusion”.
The problem
Suppose I choose the wrong 1871 census record for my 4-greats grandmother, and then, after some time realise the error of my ways. How do I decide what to delete from my file? Obviously the 1871 census event goes. But will I remember that I’ve prematurely killed off my 4-greats grandfather because I saw that the erroneous person was a widow? Or is there other evidence that does kill him off? And what about the 1881 census for 4-greats grandmother? Is that one really her? Or is it the 1871 erroneous person again that I identified using data collected from that incorrect 1871 census record?
It would be nice to select the 1871 census record and follow through the consequences of getting it wrong – where was the 1871 record itself used? Not only that but where have we used
any information that depended on that 1871 record? Did our argument for saying the 1881 census was her, depend on the 1871 record or not?
The problem is that if we have all the data for 4-greats grandmother held in one place, against one person, it gets difficult to disentangle everything. But, if we had the data in some sort of a tree (say), we would find the problem census record and follow it up the tree, seeing where it was used, not just directly, but indirectly as well.
It is the aim of the “evidence and conclusion” idea to allow someone to construct just such a tree, to allow them to trace what might be called into question if we find an error.
BetterGEDCOM
Many of us would like the BetterGEDCOM data model, and the corresponding physical file formats, to be able to accommodate the “evidence and conclusion” ideas.
Q: “If I use an application program that supports BetterGEDCOM, do I have to use evidence and conclusion ideas?”
A: Absolutely not. As I said above, the vast majority of family history files don’t use them now, and we’ve got to be able to convert those files into the new BetterGEDCOM file formats for import, export or storage. We can’t tell everyone to re-enter all their data in “evidence and conclusion” mode. Also, the majority of family historians just aren’t going to be interested in working like this, they’re content to just enter all their conclusions (working hypotheses) against one person record.
So the BetterGEDCOM data model and the corresponding physical file formats must be able to accommodate working in both “evidence and conclusion” mode and the old-fashioned way – let’s call it “conclusion only” mode.
More formally, the BetterGEDCOM data model must
allow people to distinguish between evidence and conclusions but must
not mandate them working in that mode.
A Process
I understand that Elizabeth Shown Mills writes "Sources provide Information from which we select
Evidence for Analysis. A sound
conclusion may then be considered Proof" (from "Evidence Analysis: A Research Process Map” in “Evidence Explained”) (my italics).
We all of us do something like this – perhaps some more successfully than others. There are lots of possible processes that might describe how we work – some more helpful than others. I’ll use this process description because it helps to explain working in “evidence and conclusion” mode.
Like any process, this has sub-processes (“select
[Evidence for Analysis]” and “Analysis”) and it has inputs and outputs. Let’s look at the “Analysis” sub-process. Its inputs are the Evidence that we’re going to analyse and its outputs are the Conclusions from that Analysis. When we are working in “evidence and conclusion” mode, we want to permanently record the Evidence input to the Analysis sub-process and the Conclusions output from that Analysis, keeping them clearly separate. And we need to record the logic of the Analysis as well.
Evidence is input to analysis, Conclusions are output from analysis
How do we record our input Evidence and our output Conclusions in the BetterGEDCOM files? Or other files equivalent to BetterGEDCOM?
Bearing in mind that we want to keep input Evidence and output Conclusions permanently separate, the proposal is this:
If the input Evidence is held in (say) one or more Person records, then the output Conclusions are entered into a
completely new Person record that contains all the accepted data from the input Persons and excludes any data from the input Persons that our analysis has rejected.
If an application uses BetterGEDCOM as its native file format, then the proposal describes how the application program stores its data.
If an application only uses BetterGEDCOM as a means to import and export data as a means of data transfer, then it must be
able to read or write a BetterGEDCOM file that contains data with input Evidence and output Conclusions permanently separated on different Person records as per the proposal. Hence, it will
probably do something similar on its own files.
Example
- John Smith is first found as a 5y old, in the 1880 census, living in New York. The information relating to John is manually extracted from the source, and a person entered into the application’s file containing only that data from 1880;
- A baptism for a John Smith is found in New York in 1875. Is this the same John? We don’t know yet. The information relating to this John is extracted from the source, and another person entered into the file containing only that data;
- We then mentally select the information from those two records, because we believe that they apply to the same human being;
- We do some analysis on the selected evidence and come to the conclusion (or working hypothesis) that, because of something, these two records refer to the same human. (Not sure yet where this analysis should be recorded);
- The two persons mentioned above have provided input Evidence to an Analysis, and are therefore referred to as “Evidence Persons”;
- Using the application, we then manually create a third person named John Smith where we record the details from both the baptism and census that our analysis has concluded are acceptably correct and belong to the same person. This third John Smith records the output Conclusions from an Analysis process, and is therefore referred to as a “Conclusion Person”. Again, feel free to regard this as a “Current Working Hypothesis Person” if you feel that Conclusions is too final a term but note that ESM uses the word “conclusion”;
- As part of the creation of the output “Conclusion Person”, the application must mark up the input “Evidence persons” so that they both point to the output “Conclusion Person”;
Multiple layers
If we then find the 1900 census for our John Smith, we go through a similar Analysis process, with its own input “Evidence Persons” and its own output “Evidence person”. One input “Evidence Person” will contain only the data from the 1900 census. The other input “Evidence Person” will be the current working hypothesis for John Smith, the one that contains details from the 1875 baptism
and the 1880 census. Assuming we can show the new census belongs to the same John Smith, then our
new output “Evidence person” will be another new person record containing details from the 1875 baptism, the 1880 and 1900 census.
We now have a tree of John Smith persons.
The John Smith record containing just details from the 1875 baptism and the 1880 census is now an output “Evidence person” from the first Analysis and, at the same time, an input “Evidence Person” to the second Analysis. Because the 1875 / 1880 John Smith now points to the 1875 / 1880 / 1900 John Smith, we know that the 1875 / 1880 John Smith is no longer the
current working hypothesis.
The
current working hypothesis is simply the one at the top of the tree. The
current working hypothesis person does not point to anyone else – that is how we can distinguish that this person is the
current working hypothesis person.
And only one layer
Immediately after John Smith’s 1880 data has been entered into the file, there is only person record in the file for him. At this stage there has been no Analysis, so is this person an evidence person or a conclusion person? It is proposed that:
This record does not point to any other person and is therefore the
current working hypothesis person. Since a current working hypothesis person is usually a conclusion person, we can decide to call this person a conclusion person.
Also, since the person contains only evidence from sources, we can decide to call this person an evidence person.
To me, you have to start with a Source. From that source you gather information and put Citations, from that Source on the Facts or Events, Relationships, etc.
I don't see that in your model.
Once the Citations are in place, then a review or Evaluation of the "Evidence" or the data that is present would be made.
The Citation is a factual piece of information. The Evaluation of that citation could be positive or negative.
How does that link to the Evidence?
If I have a collection of Facts or Events, I might evaluate them individually, then see if they make sense to determine that the gathered pieces of information are evidence for this person.
After I evaluate the pieces, I might, or might not draw a conclusion.
But that conclusion is date / time bound because I might find data later that is for or against what I have gathered before.
I am probably NOT going to conclude anything with the first piece of information for that person. I can only guess, that the conclusion will change over time. I also may or may not even draw a conclusion.
Russ
Russ
Evidence is a concept I continue to struggle with. I am more or less convinced that evidence is at the bottom of a "source chain." I don't think there has been any discussion of the idea of a source chain on the BG wiki yet, but it shows up in similar discussions from time to time. The idea of a source chain or source tree is that sources exist at different levels in a hierarchy. For example, a library can be a source, a set of volumes in the library can be a source that uses the library as a source, a book in a set of volumes can be a source, a chapter, page or paragraph in the book can be a source, with these descending sources linked together in a tree. To me "evidence" is the bottom source item in this hierarchy and is so granular that we can finally extract event and persons records from it. I guess I have a very practical definition of evidence -- it is the source, at whatever level I may choose to consider it, from which I extract event and person records and put them into computer records. To me a citation is a piece of text that describes that evidence within its overall source chain using the kinds of rules established by Elizabeth Shown Mills in her many publications about citing sources and explaining evidence. I think it is a goal in the definition of source entities in the BG model, that the source chains (which I do believe is a good idea) have the proper sets of attributes at the proper levels that the text of "professional level" citations can be automatically generated by reporting software.
A conclusion object is an object that the researchers builds out of evidence. Therefore its an object that doesn't have a source reference (citation) pointing into the world of paper, books, libraries, microfilm, photos etc. Yes, its ultimate constituent parts refer to those things for their sources and justification, but a conclusion object is based only on a reasoned decision a researcher made. The reason and justification he used in making that decision is the only reasonable thing to use as a citation. What normally happens of course, is that the real citiations for the evidence items are shown in the list of sources and we all seem to just realize that the researcher has decided for us that the his/her conclusion persons refer to that evidence. Take a look at articles in any genealogical journal, especially those that purport to show the descendancy from an ancestor. Most articles like this are in the "Register" format. As you read these articles a consistent pattern arises. The author describes all the items of evidence he/she has found and then implicitly or explicitly shows how he/her has decided to group these evidence records in order to decide who was who and how they fit into families. When you look at the list of sources at the end, all you see are the sources of evidence, but the whole article has been chocker block full of conclusions that author has made about how to interpret the evidence. To me the fact that the justifications for these conclusions are not always explicitly stated is a bit of a lack, but these various publication forms of genealogical research have a long tradition.
Tom Wetmore
We'll get there, I am sure, or I sure hope so.
To me, a "list of sources" is a bibliography.
To me, what is listed in a report from a genealogy program, in the form of a Footnote or EndNote, as the Citation. The format of that Citation has been documented in Evidence Explained! by Elizabeth Shown Mills.
A Citation to me, does not detail what I took out of what ever I am looking at, as I entered that information into fields that my program gives me, in the form of Facts or Events.
I might put the details of what I found in that Source, in a specific place in that Source, the word for word information that I found there, but that might be a free form set of notes so that I could see what I found. But the Facts or Events would be in their own Facts or Events fields that the program gave me. I would then attach the Citation to those FACTS. In order for be to enter a Citation, the Source would already have to be in my file, or I enter the Source Information as I enter the Citation.
Since I haven't seen, nor talked with anyone who has software that deals with the Evaluation of Evidence, nor reaching of a Conclusion, and mine certainly doesn't have these two features, I am not sure what that would look like. All I know is that I need to Evaluate, and I do, my Sources (as a whole) and the Citations specifically, when I think I know who this person really is. I do have a way to mark the Facts / Events that I think are true, but not a good platform to do that evaluation and reach some sort of conclusion.
Russ
I'm slightly handicapped by only knowing ESM's earlier book, "Evidence - Citation & Analysis for the Family Historian", but in that book, as I recollect, ESM produces templates for lots of types of citations as they will appear in a finished report. (Whatever "finished" means!)
Nowhere, as I recollect, does ESM discuss the names for bits of data that get entered into a computer program. (Nor should she - she's defining the end-result).
The problem arises with the mis-use that some programs make of the term "citation" and the contortions that some of us go through to avoid making the same error. In software like PAF (if I recall correctly), one enters a Source with all the detail that says the title of the book, which library it was found in, etc. When the fact is entered later, PAF and other programs allow the user to specify which source is being used, what the page number is within that source, whether it's primary, etc, etc. It refers to this entry as a citation - but it isn't because if you look at the GEDCOM it only reads something like "page 36, source S123, secondary" (I'm anglicising the tags). It doesn't tell you where the book is, when it was published, etc, in other words it's only half the citation as required by ESM. Yet PAF and others still refer to it as a citation.
Now, you may well write the full ESM format citation against each fact in addition, but for those that don't, the software attempts to come up with an ESM format citation by blending "page 36, source S123, secondary" with the requisite info from the source.
What I'm trying to do is come up with a name for "page 36, source S123, secondary" that is different from "citation". The name isn't in ESM because (in my book at least) she doesn't consider these intermediate stages. Hence, I may come up with terms like "source reference" to refer to the "page 36, source S123, secondary". If I do, I shall try to define it clearly...
Incidentally - what PAF etc try to do is actually sensible - the publication info etc should only be entered once, and that's against the source, not against every single fact that comes out of this source.
The Citation wouldn't tell you where Source is by the Bibliography would.
The Source List or the First Use of the Reference Note WOULD tall you where the source is.
From the QuickSheet, Citing Anestry.com Databases & Images.
Source List entry:
Author or Creator
Item Title
Item Type
Website Title
URL
Date
This information would let the reader know that the information came from Ancestry.com (Website Title, and the URL)
The First Reference:
Author or Creator
Item Title
Item Type
Website Title
URL
Date
--- so far so good
Specific Item of Interest
Credit Line
Source of the Source
With this data entry, defining the Source, the Citation would provide the specifics relating to the Event being cited.
I look at it this way. If I send you my research, I want you to be able to look at my Source and Citation, and see exactly what I recorded, fact / event by fact / event, if I send everything in my file. If I select which facts / events that I want, you should be able to tell, in the Source / Citation where I got my information from. You can accept or reject my research. That isn't the point, but I do want you to know where I got the information so that you can go look it up for yourself.
Why? It my be a Source that you hadn't looked at before. Or, you may have found that this source is great or unreliable. I can to my conclusion, you can make your own conclusion.
We're trying to get away from the fact that today, the GEDCOM that I send to another researcher, my source and citation information was a real mess, and of no use to the person receiving the information.
I agree with you that the term "citation" is older software was flawed, but that is what we are trying to help them out with.
If we define what a Source is, based on current genealogical standards, and what a Citation is, based on current genealogical standards, we, the users, will be able to share our information without it getting messed up.
Since some software developers have provided their uses with a Template to enter Source and Citation information based on Evidence Explained!, the BetterGEDCOM effort should continue using the "common" terms that have been defined.
That doesn't mean totally accepted, but if the developers of software have gone this far, and we want them to participate in this effort, we should use terms that understand.
Russ
We also agree that the older use of "citation" was flawed.
And I absolutely agree with your methodology.
What I'm driving at is that the way the _data_ _model_ will come out, is that the ESM conformant "First Use of the Reference Note" will be made up of a bit entered when the source was entered (title of source,etc), and a bit entered when the fact is entered (page number, quality, etc). That 2nd bit is not an ESM conformant citation so I will need a name for it later on, so I can't use "citation" and I have to create a new term that ESM didn't _need_ to define.
I've only now really read the articles about evidence management at Ancestry Insider. I found this one particularily helpful for defining "evidence" among other terms:
http://ancestryinsider.blogspot.com/2010/05/evidence-management-explained.html
The definitions of source and citation are given as:
"A source—or its original—is something or someone you can touch."
"A citation is something you read that tells where to find the source."
Tom's idea of a "source tree" is very interesting. It seems like it could save a lot of repetitious work, while clearly defining the exact "source" (the physical thing) and the "citation" down to the page, line and letter.
(I think what you take out of the source that has been referenced as such, is a piece of "evidence".)
As long as every level in that tree is a physical thing (or its copy), I guess it's right to name it a "source tree". The whole path through that tree would be the citation.
Could every source (or just the top level(s)?) have a location, too? E.g. the library has an address, the book is in a numbered shelf, the page -- ok, the location of the page is obvious.
If you've got a paper copy of a microfilm of a church register, how would you put this into the structure?
And what about the JPG scan of that paper copy?
Maybe we need a list of real-life examples for sources to see how to best address them.
http://www.lineascope.com/
"Lineascope is an online application for capturing, analyzing, and presenting chains of genealogical information and evidence."
It seems interesting from the outside. I've not played with it (don't have a google account), but maybe someone else is interested?
You said:
"Since some software developers have provided their uses with a Template to enter Source and Citation information based on Evidence Explained!, the BetterGEDCOM effort should continue using the "common" terms that have been defined."
Unfortunately, those templates provided by the software developers suffer from the same flaw as the GEDCOM- namely, they are each the particular developer's interpretation of Mills.
For example, just look at the difference between those provided By Legacy's SourceWriter and those provided by FTM.
Sorry, don't have Legacy to see the SourceWriter.
I am not disagreeing with you. I don't now.
When you compared the two, what was the difference in a GEDCOM output, today.
That also doesn't mean that this project can't help make the changes.
I hope so, any way.
Thanks Andy.
Russ
As you know, my main program is TMG although I do use FTM for the relationship calculator.
I don't use GEDCOM at all except to load basic trees to Ancestry's Member trees so I didn't even bother to compare GEDCOM output of the two programs- I didn't need to, all I had to look at was the Source Templates they provided to see how different they were and from that I could tell that both would be mangled when fed into a GEDCOM and wouldn't look like themselves OR each other when they came out the other end.
And what you posted is one of the problems we are trying to get at. Mangling any of our research.
Russ
Russ - I too am uncertain yet about where citations go in the Evidence & Conclusions model. However, I can say what I believe should apply to your last comment quoted above.
When a person is initially created from, say, a new child first seen on a census form, and only there so far, clearly there will be only one instance in the file (so far as we know) of this person.
In this case, the child is entered into the file, taking the details from the single census source and so counts as an evidence-type person.
However, the data from the same child does not get used anywhere else, so they are also a conclusion-type person. It's not much of a conclusion, of course, since it's just taking the data, as read, from the source, but it is your initial "conclusion".
If you work the model this way, then (a) someone can be both evidence and conclusion at the SAME time and (b) you don't actually do anything to make that first conclusion.
You may think this is a bit of a cheat in terminology - sorry, but I was trained as a mathematician and cheats like this are what we do all the time to save work!
Later on, you may find a baptism for someone of the same name, in the same area, at roughly the right time, with the right parents' names. You'd enter the baptism source and a new evidence person that just extracts the details from the baptism.
Then, once you have done some further analysis and concluded that this John Smith baptised in New York in 1875 is really the same as your John Smith who is 5y old living in New York in the 1880 census, then you can create a 3rd person to combine the data from the previous two. Because this uses the data from the previous two, then this 3rd one is a conclusion person, and the 1st 2 automatically stop being conclusion persons and are just evidence persons.
Where I am unsure is what citations should get attached to the conclusion person.
Oh, and if you get the 1900 census for our mythical John Smith, you'd create yet another evidence person that just extracted the details from the 1900 census, and in my personal view, once you'd made sure it's the same John Smith again, you'd just add the 1900 data to the existing conclusion person.
Sorry, I am still confused and probably with terminology. And, where tasks are performed.
I my mind, it goes like this:
Source (a document with information)
Citation (where in the Source did I find this information)
Citations are attached to Facts or Events
Those Facts or Events may or may not, as entered into some databases, be complete. A Census record will NOT give you complete Birth Information.
Lets say that these Citations are "Evidence" about this person, facts or events in that persons life.
This information is entered into my database.
Gathering of more information from more Sources continues.
So far, as far as I am concerned, there is NO conclusion. I don't want the software to draw any conclusion for me.
At some point, I then need to Evaluate the Evidence.
From what I can tell, there aren't any genealogy programs that have tools for us to do this Evaluation. We may have places to make notes on our Sources or Citations (Evidence) by not platform to do this Evaluation. It would be for the User to stop, for a moment, and do this evaluation.
The software folks, and this is why this discussion is important for the BetterGEDCOM, need to develop some sort of tools to help with this evaluation.
The software that I use has a place where I can mark a citation on a scale of 1 to 5. I don't know about other programs.
I also have a feature to mark a Fact or Event as the "preferred" Fact or Event when the same Fact or Event is used by the same person. If the Fact name or Event name is used only once, it is marked as "preferred". The user can change that. But the program insists that the use of a Fact or Event is Preferred.
That is OK, but is not a Conclusion. The program made a decision about the fact / event with the citation.
The user needs to do the evaluation, and if the program developers give us a platform to look at the "big picture" of the individual, we should then be able to draw a conclusion based on the evidence at hand.
At this point is where the BetterGEDCOM comes into play for the Conclusion aspect about this individual.
I think that the BetterGEDCOM needs to be 'ready' to handle a "conclusion", but at what level. The Fact or Event level, the piece parts, or at the Person Level.
What I think might happen is this, when the file is being generated for transport:
Identify the Person, link or what ever term you want, the Facts or Events AND the Evidence for the Facts or Events to that person.
Then, some sort of indicator that gets to the next step, IF the program has this type of feature (conclusion).
The software should allow me to mark the events or facts that allow me to conclude that these pieces of information belong to this person. So the "conclusion" record (may not be the right term) should be marked and put into the string a data to be sent to the other user. This Conclusion Record should (must) include a Date / Time Stamp, based on when the User Marked that information as a conclusion.
If there is not conclusion record, a Null Record could be sent or not record could be sent. That determination, I think, should come from the BetterGEDCOM.
No "conclusion" record, don't sent anything, or a flag that says "no conclusion record".
I think that my confusion comes from your term "Conclusion Person".
I am not sure that the BetterGEDCOM can demand that a Citation be put on each Event or Fact, but IF there is a Citation on an Event or Fact the BetterGEDCOM MUST send it along, in the format that the software presents it.
One User's opinion.
Russ
Tom Wetmore
Can we start to try to use common terms for 'things'.
To me, a Source is a document, book, or records. A Citation defines where in that Source I found recorded information.
Your term "source references", ot me, is confusing.
I can translate Evidence to Citation in my terms.
I still don't understand what the term "Conclusion person" means.
Sorry, just trying to understand your terms.
Thank you,
Russ
Russ - one reason for Tom using the term "source reference" is that "citation" is _not_ supposed to be where in the source you find the info. If you look at "The Ancestry Insider" (on http://ancestryinsider.blogspot.com ) and find the post for 26 May 2010, you'll find an explanation of what a citation really is. This isn't just me, Tom and The Ancestry Insider, but it springs from Elizabeth Shown Mills herself.
If I attempt to very roughly summarise (and possibly get it wrong), a "citation" (in its correct usage) gives the full info for finding the bit of information that you're looking for. Not just the page number in the source, but where that source is held, what it's called, when it was published, etc.
On the other hand, lots of software (PAF, Ancestry and ?) just define the citation as where in the source we find the info. And omit the "where is the source?" bit because (reasonably enough) you probably already wrote that down when you entered the source into your software.
Now - here's my take on it - I really don't care about the difference between the correct use of the term citation and the incorrect, because it's all entered into the program in the same way! And we're years too late to change common usage. But some people do care and so they use terms like "source reference" instead to point to which source and where in the source. And I may have got Tom's usage incorrect - if so, apologies.
In summary - I'm getting too old to expect everyone to use the same terms so frankly I've no problem with you using the term "citation" because I can translate it to my terms. Which I haven't written down yet...
For purposes of this discussion:
1. “citations are statements in which we identify our source or sources or…particular [information].”
2. “a citation states where you found [the cited] piece of information.”
- information –
1. “knowledge obtained from investigation.” 2. “the content of a source—that is, its factual statements or its raw data.”- evidence –
1. “something that furnishes proof.”2. “information that is relevant to the problem.”
3. analyzed and correlated information assessed to be of sufficient quality.
4. “the information that we conclude—after careful evaluation—supports or contradicts the statement we would like to make, or are about to make, about an ancestor.”
- conclusion –
1. “a reasoned judgment.”2. “a decision [that should be] based on well-reasoned and thoroughly documented evidence gleaned from sound research.”
I don't see anywhere in here Source-Reference.
A number of software vendors are now providing their users with templates to enter their Source information, and Citations, based on Evidence Explained!
I guess that the point of what I am trying to make is why invent other terms for things that are almost "Standards". Many folks, doing family research might agree that EE! is 'the standard'. That is complimented by our software vendors providing Templates based on that 'standard'.
Is the "Source Reference" the presentation of the Source and Citation, as found in Evidence Explained! Source Entry List, First Reference Note, and the Subsequent Note?
Russ