<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>The Sente Blog</title>
    <link rel="alternate" type="text/html" href="http://www.thirdstreetsoftware.com/blog/" />
    <link rel="self" type="application/atom+xml" href="http://www.thirdstreetsoftware.com/blog/atom.xml" />
    <id>tag:www.thirdstreetsoftware.com,2008-08-19:/blog//1</id>
    <updated>2008-11-19T20:26:19Z</updated>
    <subtitle>Discussions of Sente, academic reference management, on-line research, bibliographies and related topics.</subtitle>
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.2-en</generator>

<entry>
    <title>Sente Available on Amazon.com</title>
    <link rel="alternate" type="text/html" href="http://www.thirdstreetsoftware.com/blog/2008/11/sente-available-on-amazoncom.html" />
    <id>tag:www.thirdstreetsoftware.com,2008:/blog//1.20</id>

    <published>2008-11-19T20:08:41Z</published>
    <updated>2008-11-19T20:26:19Z</updated>

    <summary>We are pleased to announce that it is now possible to purchase Sente on CD-ROM through Amazon.com (at least in the US).For many people, downloading and purchasing a license on-line will remain the best option, but we regularly receive requests...</summary>
    <author>
        <name>Michael</name>
        
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://www.thirdstreetsoftware.com/blog/">
        <![CDATA[We are pleased to announce that it is now possible to purchase Sente on CD-ROM through Amazon.com (at least in the US).<div><br /><div style="text-align: center;"><img onload="if (typeof uet == 'function') { uet('af'); }" src="http://ecx.images-amazon.com/images/I/41gPs8ECiZL._SL500_AA280_.jpg" id="prodImage" width="280" height="280" border="0" alt="Sente 5, Academic License (Mac)" /></div><div><div style="text-align: center;"><br /></div><div>For many people, downloading and purchasing a license on-line will remain the best option, but we regularly receive requests for an actual physical package, and this option fills that need.</div><div><br /></div><div>Here is the <a href="http://www.amazon.com/Sente-5-Academic-License-Mac/dp/B001GPM03S">Sente p</a><a href="http://www.amazon.com/Sente-5-Academic-License-Mac/dp/B001GPM03S">roduct page on Amazon.</a></div><div><br /></div><div>Amazon's Sente page says that it has been available since September, but given that they only received the product from us two days ago, this is not really the case.</div><div><br /></div><div>You will notice that as of today, no reviews have been posted.  Existing customers, no matter how they purchased the product, can always post their thoughts on Amazon, should they be so inclined...<br /><div><br /></div><div><br /></div></div></div></div>]]>
        
    </content>
</entry>

<entry>
    <title>Improved Note Taking</title>
    <link rel="alternate" type="text/html" href="http://www.thirdstreetsoftware.com/blog/2008/11/improved-note-taking.html" />
    <id>tag:www.thirdstreetsoftware.com,2008:/blog//1.19</id>

    <published>2008-11-14T19:05:52Z</published>
    <updated>2008-11-16T22:29:30Z</updated>

    <summary>I would like to say a few words about our latest release, which includes a major update to Sente&apos;s note-taking features.Since the release of version 5.0 in 2007, Sente has included the ability to attach multiple notes to each reference....</summary>
    <author>
        <name>Michael</name>
        
    </author>
    
        <category term="General Reference Management" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="On-line research" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="notespdf" label="notes pdf" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://www.thirdstreetsoftware.com/blog/">
        <![CDATA[I would like to say a few words about our latest release, which includes a major update to Sente's note-taking features.<div><br /><div>Since the release of version 5.0 in 2007, Sente has included the ability to attach multiple notes to each reference. (Earlier versions restricted you to a single note per reference.) Each note included a title, page range, quotation and comments.</div><div><br /></div><div>For many users, this has been a valuable feature, and they mention it regularly in posts about Sente. But we have never been particularly fond of Sente's interface for creating and editing notes. It worked, but it was neither attractive nor terribly functional.</div><div><br /></div><div>In Sente 5.7, we have completely rewritten the notes interface and we are much happier with the results.  In the new interface, it is easy to see more than one note at a time, and we make better use of limited screen space.  Also, it is now possible to copy one or more notes from within the Notes view, and then to paste them into most other applications.</div><div><br /></div><div>We have also added a feature that makes it simple to create notes from selections in PDFs or web pages. You can select either text or any arbitrary region in either a PDF or a web page, and then, if you click on the Create Note button, Sente will automatically create a new note for the current reference using the selection as the quotation.  Sente will also fill in the page numbers and add a placeholder title for you.</div><div><br /></div><div>This ability to create notes from PDFs is not intended as a replacement for tools that let you mark-up a PDF, like Preview and Skim.  If what you want to accomplish is to highlight portions of a PDF so that the next time you read the document you will see these annotations, then we would recommend that you use one of these other tools.  (Annotations created in Preview, unlike those created in Skim, will show up in the Links view within Sente, so you will not need to return to Preview to view them.)</div><div><br /></div><div>These changes should make Sente's notes feature more useful to many of our users.  I would encourage you to watch the <a href="http://www.thirdstreetsoftware.com/site/videos/notes.html">new video</a> on our web site and then to download the latest version and give it a try.</div></div>]]>
        
    </content>
</entry>

<entry>
    <title>User Interface Design: Inactive Controls</title>
    <link rel="alternate" type="text/html" href="http://www.thirdstreetsoftware.com/blog/2008/11/user-interface-design-inactive-controls.html" />
    <id>tag:www.thirdstreetsoftware.com,2008:/blog//1.18</id>

    <published>2008-11-02T18:23:40Z</published>
    <updated>2008-11-02T19:18:46Z</updated>

    <summary>We are in the middle of implementing some new features in Sente and we are faced with a common design dilemma that I am surprised has not, at least as far as I am aware, been resolved in a standard...</summary>
    <author>
        <name>Michael</name>
        
    </author>
    
    <category term="userinterface" label="user interface" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://www.thirdstreetsoftware.com/blog/">
        <![CDATA[We are in the middle of implementing some new features in Sente and we are faced with a common design dilemma that I am surprised has not, at least as far as I am aware, been resolved in a standard way across all applications.<div><br /></div><div>The issue is what to do about controls for operations when those operation cannot be performed.</div><div><br /></div><div>The basic answer in Cocoa is that controls (menu items, buttons, etc.) for operations that cannot be performed should be disabled.  Thus, when writing in a text editor, if there is no test selected, the Edit > Copy command is greyed out, meaning there is nothing that can be copied right now.</div><div><br /></div><div>The problem with this approach is that it does not really help the user very much.  They know that they cannot perform the operation, but they do not know why and what they need to do to be able to perform the operation.  For me personally, this is one of the most common problems I face when trying out new software.  It may be obvious to the developer why the greyed out operation is not available right now, but I am often at a complete loss as to why this would be the case.</div><div><br /></div><div>I have heard people suggest that you leave the command active (i.e., not greyed out) and pop up an error sheet when the command is invoked inappropriately.  The problem I have with this option is that you lose the quick feedback that an inactive control gives you -- you have to go down the blind alley to find out that it leads nowhere.  Particularly after you understand when a particular command makes sense and when it does not, deactivating it when it is invalid is helpful.</div><div><br /></div><div>Another approach I have heard of fakes the deactivation but leaves the command executable.  For example, if Copy made no sense, it would appear grey in the menu, but it could still be selected.  The developer would then open an error sheet (or something similar) to explain why the command can not be executed.  While there is much that I like about this approach (immediate feedback of "deactivation"; simple, consistent method for getting more information) it also has some important problems.  One, it is not standard, so most users will not know that they can select an inactive control.  Two, it is not supported in the Cocoa frameworks, so it would require quite a bit of development on the part of every developer to make it work.  Three, there is no visible indication that an explanation is available, so less experienced users would have to be told that this convention existed.</div><div><br /></div><div>One more approach is to use the fly-over help on controls to explain when they can be used.  This could be very helpful, but... One, it does not work for menu items (they do not have flyover help).  And, two, because this is not a standard, many people will not find the messages even where they exist.</div><div><br /></div><div>So, in the end, I don't think any of these options is good enough and I cannot think of anything better.  What I really want is a solution that:</div><div><br /></div><div>1) is genuinely standard, and this means that it is implemented in the Cocoa frameworks so that everyone gets it "for free" just by following the normal development process and experienced users expect it to be used</div><div><br /></div><div>2) preserves the immediate feedback of inactive controls</div><div><br /></div><div>3) is obvious (or at least visible) for users who do not yet know how to get this information</div><div><br /></div><div>Anyone have any ideas about what such a mechanism might look like?  Or do you think I am making too much of this problem and that the existing conventions/tools are adequate?</div><div><br /></div><div>Michael</div>]]>
        
    </content>
</entry>

<entry>
    <title>Sente Undergraduate Edition</title>
    <link rel="alternate" type="text/html" href="http://www.thirdstreetsoftware.com/blog/2008/10/sente-undergraduate-edition.html" />
    <id>tag:www.thirdstreetsoftware.com,2008:/blog//1.17</id>

    <published>2008-10-22T16:17:07Z</published>
    <updated>2008-10-23T21:26:45Z</updated>

    <summary>We have just released the Undergraduate Edition of Sente and I wanted to say a few words about this new version of Sente.Since we first launched Sente back in 2004, our focus has been on providing the best reference manager...</summary>
    <author>
        <name>Michael</name>
        
    </author>
    
        <category term="General Reference Management" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="undergraduateedition" label="undergraduate edition" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://www.thirdstreetsoftware.com/blog/">
        <![CDATA[We have just released the Undergraduate Edition of Sente and I wanted to say a few words about this new version of Sente.<div><br /></div><div>Since we first launched Sente back in 2004, our focus has been on providing the best reference manager for the most demanding users.  This has lead to the development of features like standing searches, hierarchical libraries, targeted browsing and automatic PDF import, to name a few.  During this time, the growth in the use of Sente by graduate students, professors and research professionals has been dramatic.</div><div><br /></div><div>But we have heard from many undergraduates over the years who really like Sente's features and intuitive user interface, but who cannot justify the cost of the software because they will only use it to gather the references for a handful of papers each year.  These users are not really interested in setting up standing searches or importing large collections of PDF files; they just want an alternative to EndNote.</div><div><br /></div><div>To make Sente more affordable for this type of user, we are now offering Sente Undergraduate Edition, which has all of the features of Sente, but has a limit of 250 references per library.  This limitation, while too restrictive for most graduate students and researchers, is more than enough for most undergraduate papers.</div><div><br /></div><div>Sente Undergraduate Edition is not limited in any way other than the size of the library that can be created.</div><div><br /></div><div>Sente Undergraduate Edition is available now from Kagi for $34.95.  The Undergraduate Edition can be upgraded to the regular academic version for $64.95.</div>]]>
        
    </content>
</entry>

<entry>
    <title>Sente 5.6 and the Release Process</title>
    <link rel="alternate" type="text/html" href="http://www.thirdstreetsoftware.com/blog/2008/09/sente-56-and-the-release-process.html" />
    <id>tag:www.thirdstreetsoftware.com,2008:/blog//1.16</id>

    <published>2008-09-17T16:41:11Z</published>
    <updated>2008-09-17T16:57:10Z</updated>

    <summary>We are very pleased to have released the first official version of Sente 5.6 with all of the new features that you have seen during the prerelease period, if you were getting the incremental updates.  I just thought I would...</summary>
    <author>
        <name>Michael</name>
        
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://www.thirdstreetsoftware.com/blog/">
        <![CDATA[We are very pleased to have released the first official version of Sente 5.6 with all of the new features that you have seen during the prerelease period, if you were getting the incremental updates.  I just thought I would write a few words about they way we developed and released this version of Sente and invite your feedback on the process.<div><br /></div><div>We began posting preview versions of 5.6 back in mid-June.  Rather than waiting until all of the features we wanted to put into this version were done, we decided to roll them out incrementally as previews.  We did this for at least two reasons:</div><div><br /></div><div>One, we really wanted user feedback on some of the new features before they were locked down as official.  Specifically, we were concerned about the targeted browsing interface.  Did we have the right interface?  Would it actually work in the wide variety of contexts our customers operate in?  We were concerned about waiting weeks or months before getting it out only to find that we had made some fundamental errors in our design.  The feedback we received during the preview period was, indeed, very helpful to us as we refined our design, so I think we achieved our goal on this one.</div><div><br /></div><div>Two, this was a very big release and we did not want to wait three months between major updates.  By putting out preview releases, we were able to incorporate numerous bug fixes unrelated to the new features, and squeeze in quite a few smaller items that we heard about during the development cycle.  Getting these fixes and features did mean jumping into the preview release cycle, but we tried hard to make sure that each release was tested enough not to break anything, and we were always standing ready to rush out a quick fix in case we missed something.  Overall, I think we achieved this goal as well, although there were a few, relatively small glitches.</div><div><br /></div><div>So, all told, I think I am satisfied with how this process went.  We got good feedback throughout the process and were able to incorporate much of it into the product.  And users benefitted from the new features as they became available.  And I am aware of only a few cases where the preview-nature of the release caused people problems.</div><div><br /></div><div>If you have thoughts on how this release was handled, please let us know.</div><div><br /></div><div>Michael</div><div><br /></div>]]>
        
    </content>
</entry>

<entry>
    <title>Designing Formats to use Ibid.</title>
    <link rel="alternate" type="text/html" href="http://www.thirdstreetsoftware.com/blog/2008/09/using-ibid.html" />
    <id>tag:www.thirdstreetsoftware.com,2008:/blog//1.15</id>

    <published>2008-09-11T04:07:20Z</published>
    <updated>2008-09-12T04:01:33Z</updated>

    <summary>One of the recent changes to the Sente bibliography format editor was in the way Ibid is handled.There is now a format-wide setting (in the General tab in the format editor) that indicates that the format uses the term &quot;Ibid.&quot;...</summary>
    <author>
        <name>Michael</name>
        
    </author>
    
        <category term="Techniques" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.thirdstreetsoftware.com/blog/">
        <![CDATA[One of the recent changes to the Sente bibliography format editor was in the way Ibid is handled.<div><br /></div><div>There is now a format-wide setting (in the General tab in the format editor) that indicates that the format uses the term "Ibid." or some variation when the same reference is cited twice in a row in a document.  This flag can also be used in cases where citing the same reference twice in a row does not use Ibid, but most of the details of the reference are to be omitted.  More on this below.</div><div><br /></div><div>In the simple case, you might want something like this:</div><div><br /></div><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;">4. <span class="Apple-style-span" style="font-family: 'Trebuchet MS'; font-size: 12px; ">Perry, Gillian, and Michael Rossington. <i>Femininity and Masculinity in Eighteenth-Century Art and Culture.</i> Manchester, New York: Manchester University Press, 1994, pp. 37-38.</span></blockquote><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><span class="Apple-style-span" style="font-family: 'Trebuchet MS'; font-size: 12px;">5. Ibid., pp. 82-84.</span></blockquote><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><span class="Apple-style-span" style="font-family: 'Trebuchet MS'; font-size: 12px;"><br /></span></blockquote>To achieve this, you need only check the Use Ibid box in the General tab in the format editor, and enter "Ibid." into the text box found there.<div><br /></div><div>In this case, everything will just work as one would hope.  Specifically, when a citation is repeated, Sente will automatically suppress every element in the selected format except for Cited Pages.</div><div><br /></div><div>If you need the format of the Cited Pages element to vary depending on whether the citation has been repeated, you can add more than one Cited Pages element to the format, and make one apply in the context of "Ibid" and the other appear in the context of "not Ibid".  For example, if you needed a preceding comma normally, but not one in the case of Ibid, you would need to create two Cited Pages elements and apply the correct conditions.</div><div><br /></div><div>Chicago 15 N (Notes) is a good example of using Ibid in this way.</div><div><br /></div><div>A variation on this can be found in Chicago 15 AD (Author-Date).  Here is a portion of a document with the temporary citation tags in place:</div><div><br /></div><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica">and {Perry 1994@32} now is the time {Perry 1994@56}</p></blockquote><div><br /></div><div>Note that different pages are being cited, but the reference is the same.  After scanning in Chicago 15 AD, the result is:</div><div><br /></div><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica">and (Perry and Rossington 1994, 32) now is the time (56)</p></blockquote><div><br /></div><div>In this format, repeated citations do not actually use the string "Ibid." but everything other than cited pages is left off the second citation.  In this case, the text box after the Use Ibid box is left empty to indicate that the citation details (other than cited pages) should be replaced with nothing.</div><div><br /></div><div><br /></div><div><br /></div>]]>
        
    </content>
</entry>

<entry>
    <title>The New Bibliography Fields View</title>
    <link rel="alternate" type="text/html" href="http://www.thirdstreetsoftware.com/blog/2008/09/the-new-bibliography-fields-view.html" />
    <id>tag:www.thirdstreetsoftware.com,2008:/blog//1.14</id>

    <published>2008-09-10T18:54:50Z</published>
    <updated>2008-12-23T01:49:12Z</updated>

    <summary><![CDATA[I would like to say a few words introducing a new feature in Sente: the Bibliography Fields view in the reference editor. &nbsp;Here is a screen shot of the new view:The new view has three major sections.The top section is...]]></summary>
    <author>
        <name>Michael</name>
        
    </author>
    
        <category term="General Reference Management" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.thirdstreetsoftware.com/blog/">
        <![CDATA[I would like to say a few words introducing a new feature in Sente: the Bibliography Fields view in the reference editor. &nbsp;Here is a screen shot of the new view:<div><br /></div><div><span class="mt-enclosure mt-enclosure-image" style="display: inline;"><img alt="Picture 7b.png" src="http://www.thirdstreetsoftware.com/blog/Picture%207b.png" class="mt-image-center" style="margin: 0pt auto 20px; text-align: center; display: block;" height="554" width="312" /></span><div><br /><div><div style="text-align: left;">The new view has three major sections.</div><div style="text-align: left;"><br /></div><div style="text-align: left;">The top section is where you select one of your favorite bibliography formats. &nbsp;I would normally recommend that you select the style that you use most often. &nbsp;Here, the selected style is "APA 5."</div><div style="text-align: left;"><br /></div><div style="text-align: left;">The first field in the next section is the reference type. &nbsp;The value selected in this pop-up determines which fields are displayed in the rest of this section. &nbsp;In the screen shot above, the selected type is "journal article" so the fields relevant to journal articles are displayed. &nbsp;There may be data in fields that are not shown here, but fields that are not shown have no effect on the bibliography entry for the selected reference type.</div><div style="text-align: left;"><br /></div><div style="text-align: left;">For many reference type / bibliography format combinations, there are fields that are not used in the selected format, but are used in some other common format. &nbsp;These fields appear below a label that begins "Items below this point..." &nbsp;While you may want to enter values for one or more of these fields, the data will not appear in the bibliography entry for this reference in the selected format.</div><div style="text-align: left;"><br /></div><div style="text-align: left;">The bottom section of the Bibliography Fields view is the preview of the selected reference in the selected format. &nbsp;This preview is kept up-to-date with changes to the fields above as you leave each field after making a change. &nbsp;This lets you see just how each reference will appear in the final output in your documents. &nbsp;(Obviously, the final results may differ slightly if, for example, the selected style calls for repeated authors to be replaced with three dashes. &nbsp;The preview here is how the reference would appear if it were the only reference in the bibliography.)</div><div style="text-align: left;"><br /></div><div style="text-align: left;">The important point to remember about this new view is that the fields that are displayed are based entirely on the reference type. &nbsp;This list of fields is then prioritized based on the selected bibliography format to place at the bottom any of the fields that are not actually used in the format for the selected reference type.</div><div style="text-align: left;"><br /></div><div style="text-align: left;">If you are a Sente user who gets most of your references from PubMed, this new feature will not make a big difference to you. &nbsp;On the other hand, if you are in the humanities or any field where you regularly deal with many different types of references, and you regularly deal with complex bibliography formats, you should find this new view very helpful as you add references to your library.</div></div><div><br /></div></div></div><div><br /></div>]]>
        
    </content>
</entry>

<entry>
    <title>Screencast from a Sente User</title>
    <link rel="alternate" type="text/html" href="http://www.thirdstreetsoftware.com/blog/2008/09/screencast-from-a-sente-user.html" />
    <id>tag:www.thirdstreetsoftware.com,2008:/blog//1.13</id>

    <published>2008-09-01T18:05:46Z</published>
    <updated>2008-09-01T18:18:30Z</updated>

    <summary>One of our users, Dr. Kerim Friedman, has put together a nice screencast demonstrating the use of Sente to acquire references from Google Scholar and related PDFs from AnthroSource.  The video is included in one of his posts at Savage...</summary>
    <author>
        <name>Michael</name>
        
    </author>
    
        <category term="On-line research" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.thirdstreetsoftware.com/blog/">
        <![CDATA[One of our users, Dr. Kerim Friedman, has put together a nice screencast demonstrating the use of Sente to acquire references from Google Scholar and related PDFs from AnthroSource.  The video is included in one of his posts at Savage Minds, a site dedicated to topics in anthropology.<div><br /></div><div>You can view the screencast here:</div><div><br /></div><div><a href="http://savageminds.org/2008/08/30/how-to-import-google-search-results-into-sente/">http://savageminds.org/2008/08/30/how-to-import-google-search-results-into-sente/</a></div><div><br /></div><div>The basic flow works in many other fields, as well, so even if you are not an anthropologist, you might find the information valuable.</div><div><br /></div>]]>
        
    </content>
</entry>

<entry>
    <title>Sente in the Kleper Report on Digital Publishing</title>
    <link rel="alternate" type="text/html" href="http://www.thirdstreetsoftware.com/blog/2008/08/sente-in-the-kleper-report-on-digital-publishing.html" />
    <id>tag:www.thirdstreetsoftware.com,2008:/blog//1.12</id>

    <published>2008-08-31T18:26:24Z</published>
    <updated>2008-08-31T18:36:50Z</updated>

    <summary>A review of Sente has just appeared in the Kleper Report on Digital Publishing, a newsletter for the publishing industry.  Current issues are available only to subscribers, but here are some excerpts:Sente 5 is an application that supports the management...</summary>
    <author>
        <name>Michael</name>
        
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://www.thirdstreetsoftware.com/blog/">
        <![CDATA[A review of Sente has just appeared in the Kleper Report on Digital Publishing, a newsletter for the publishing industry.  Current issues are available only to subscribers, but here are some excerpts:<br /><br /><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 11.5px Helvetica">Sente 5 is an application that supports the management of academic references by enabling access to hundreds of worldwide on-line databases. Users simply input keywords into a search field and are returned a listing of matching references, some of which contain notes, full text, or PDF files of the reference content. PDFs can be downloaded and managed locally, on the user's computer. It is the ultimate tool for maintaining daily updates on new contributions to the literature in a given field or on a given subject. [...]</p><p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 11.5px Helvetica"><br /></p><p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 11.5px Helvetica"><p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 11.5px Helvetica">A series of informative videos (<span style="color: #0000ff">http://www.thirdstreetsoftware.com/site/videos.html</span>) show how easily and quickly the program can gather valuable research references and content. Sente is the complete solution for scholarly and everyday research needs.</p><p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 11.5px Helvetica"><br /></p><p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 11.5px Helvetica"><span class="Apple-style-span" style="color: rgb(0, 0, 0); "><div>[Reprinted with permission from The Kleper Report on Digital Publishing &lt;<a href="http://www.printerport.com/kdp">http://www.printerport.com/kdp</a>>, copyright 2008, Graphic Dimensions, Lauderdale by the Sea, FL.]</div><div><br /></div><div><br /></div><div><br /></div></span></p></p></blockquote>]]>
        
    </content>
</entry>

<entry>
    <title>Unlearning &quot;occurrences&quot;</title>
    <link rel="alternate" type="text/html" href="http://www.thirdstreetsoftware.com/blog/2008/08/unlearning-occurrences.html" />
    <id>tag:www.thirdstreetsoftware.com,2008:/blog//1.11</id>

    <published>2008-08-24T02:51:15Z</published>
    <updated>2008-08-24T04:59:12Z</updated>

    <summary>People who either created or modified bibliography formats in older versions of Sente had to understand what we called &quot;occurrences&quot; in order to accomplish many goals.  Unfortunately, this concept now needs to be &quot;unlearned&quot; to use the new version of...</summary>
    <author>
        <name>Michael</name>
        
    </author>
    
        <category term="Bibliographies" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Techniques" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.thirdstreetsoftware.com/blog/">
        <![CDATA[People who either created or modified bibliography formats in older versions of Sente had to understand what we called "occurrences" in order to accomplish many goals.  Unfortunately, this concept now needs to be "unlearned" to use the new version of the bibliography format editor.  This article is intended to help people make the transition from the concept of "occurrences" to the ideas that replace it.<div><br /><div>One of the problems that both the old and new approaches are addressing is the fact that the more complicated formats (like APA, Chicago, etc.) require that references be formatted differently depending on the context in which they appear.  For example, some formats call for a complete version of the reference the first time it appears in a document, and an abbreviated version everywhere else.  Some formats want the in-text citation to use only the author name, but in contexts where this is not sufficient to identify the correct reference, they include the title (or a portion thereof).</div><div><br /></div><div>Prior versions of Sente supported this by allowing you to specify exactly which contexts, or occurrences, a style cared about (most only cared about a few) and then it allowed / required you to create completely different formats for each one.  For example, if a format required different contents for the first vs. subsequent occurrences of a reference, one would add the "subsequent" occurrence to the format definition, and then specify exactly how references should appear in this case.  Often the definitions for many occurrences were very similar, differing in only a few details.</div><div><br /></div><div>We have now changed this approach fundamentally.  Now, instead of a potentially large number of "occurrences," a bibliography format in Sente only includes one in-text and one bibliography format for each reference type.  And the format definition for each of these can contain elements whose appearance is conditional, based on the context in which the reference appears.  That is, there is one in-text format for journal articles in each bibliography format definition.  This single format might include, say, two versions of the author list: one for the first appearance and the second for all other appearances, but all of the other details are specified only once.  This approach eliminates a lot of redundant work, and I know from experience just how hard it was to keep this redundant information in sync.</div><div><br /></div><div>Here is another way to look at it.  If you read my last post (about customizing the preview display), you will see that it is possible to set things up so that there are two different versions of the in-text format displayed.  (My example in that post was first and subsequent appearances.)  In the old version of Sente, these would have been specified completely independently.  In the new version, they are each a version of the single, in-text format specification.  Because this specification contains some elements that appear and disappear based on the context conditions, the specification can result in two or more very different outputs for any one reference, thus the need for two different previews.</div><div><br /></div><div>Now when you want to modify a format to behave slightly differently in a different context, you can leave untouched all of the elements that stay the same, and only apply conditions to those elements that should be different from one context to the next.</div><div><br /></div><div>While it may take some time to adjust to this new approach, having personally recreated the most complex formats using the new approach, I can say that I think the new approach is much better than the old one.  This change, along with all of the other recent changes to the bibliography format editor, makes creating and maintaining complex formats much easier than it has even been before.</div></div>]]>
        
    </content>
</entry>

<entry>
    <title>Customizing the Bibliography Format Preview</title>
    <link rel="alternate" type="text/html" href="http://www.thirdstreetsoftware.com/blog/2008/08/customizing-the-bibliography-format-preview.html" />
    <id>tag:www.thirdstreetsoftware.com,2008:/blog//1.10</id>

    <published>2008-08-22T18:29:17Z</published>
    <updated>2008-08-23T22:23:23Z</updated>

    <summary>In the new version of the bibliography format editor in Sente, you can customize what gets shown in the preview pane so that you can more easily see how a given format will behave when it is used on a...</summary>
    <author>
        <name>Michael</name>
        
    </author>
    
        <category term="Bibliographies" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Techniques" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.thirdstreetsoftware.com/blog/">
        <![CDATA[<p>In the new version of the bibliography format editor in Sente, you can customize what gets shown in the preview pane so that you can more easily see how a given format will behave when it is used on a document.</p>
<p>For an example, let's look at the Chicago 15 N (Notes) format. In this format, one does not normally include a bibliography at the end of the document, so all of the important bibliographic detail has to appear in the first occurrence of a citation. After that, a much shorter version of the citation can be used.</p>
<p>In this article I am not going to talk about exactly how one defines a format to work in this way. Instead, I am just going to show you how you can customize the preview pane to help you preview this behavior.</p>
<p>By default, the preview pane includes one version of the in-text format and one of the bibliography format. For the Chicago format in question, this would look like this:</p>
<blockquote>
  <p><span style="font-family: 'Lucida Grande'; font-weight: bold;">▼ Journal Article (JA)</span></p>

  <p style="font: 10.0px Lucida Grande; color: #0000ff">[edit sample data]</p>

  <p style="margin: 5.0px 0.0px 2.0px 0.0px; font: 10.0px Lucida Grande; color: #808080">In-Text</p>

  <p style="margin: 0.0px 0.0px 0.0px 20.0px; text-indent: -20.0px; font: 12.0px Trebuchet MS">John Allen Smith <i>and others</i>, "Fractals in Biological Systems," <i>J Biol Chem</i> 151, no. 22 (1999): doi:10.1006/ceth.2003.1354. http://www.jbiolchem.com/article/doi/10.1006/alpha.23.45 (accessed February 1, 2003).</p>

  <p style="margin: 5.0px 0.0px 2.0px 0.0px; font: 10.0px Lucida Grande; color: #808080">Bibliography</p>

  <p style="margin: 0.0px 0.0px 0.0px 20.0px; text-indent: -20.0px; font: 12.0px Trebuchet MS">Smith, John Allen, Randall Benjamin Jones, Alfred Carlyle Black, and Susan D. White. "Fractals in Biological Systems." <i>J Biol Chem</i> 151, no. 22 (1999): doi:10.1006/ceth.2003.1354. http://www.jbiolchem.com/article/doi/10.1006/alpha.23.45 (accessed February 1, 2003).</p>

  <p style="font: 12.0px Helvetica; min-height: 14.0px"><br /></p>
</blockquote>
<p>But this does not show you how the format will display a reference the second (or later) time it appears in your document. You could create a test document and scan it using this format, but that would be tedious. Instead, Sente lets you modify the preview to include an example of the in-text format when it appears in a subsequent occurrence.</p>
<p>To modify the previews, switch to the Advanced tab in the bibliography format editor drawer, where you will see something like this:</p>
<p style="text-align: center;"><img src="http://www.thirdstreetsoftware.com/blog/Picture 10.jpg" width="317" height="347" alt="Picture 10.png" /></p>
<p style="text-align: left;">Here you can see that I have renamed the default In-Text context to "In-Text, first occurrence" and, using the Context Conditions pop-up menu, I set the active condition to be "first occurrence." I also created a second in-text preview and set the context to be "subsequent occurrence." One can create a preview with any combination of conditions, and the sample data will be displayed as they would appear in a real document when those conditions are encountered.  When I create a preview with the condition "first occurrence in document," any element whose presence or absence depends on this condition will be turned on or off as specified.</p>
<p>I could have also removed the bibliography preview, given that one does not normally include a bibliography in Chicago Notes format, but I left it here in case someone finds it useful.</p>
<p>With these changes, the preview looks like this:</p>
<blockquote>
  <p><span style="font-family: 'Lucida Grande'; font-weight: bold;">▼ Journal Article (JA)</span></p>

  <p style="font: 10.0px Lucida Grande; color: #0000ff">[edit sample data]</p>

  <p style="margin: 5.0px 0.0px 2.0px 0.0px; font: 10.0px Lucida Grande; color: #808080">In-Text, first occurrence</p>

  <p style="margin: 0.0px 0.0px 0.0px 20.0px; text-indent: -20.0px; font: 12.0px Trebuchet MS">John Allen Smith <i>and others</i>, "Fractals in Biological Systems," <i>J Biol Chem</i> 151, no. 22 (1999): doi:10.1006/ceth.2003.1354. http://www.jbiolchem.com/article/doi/10.1006/alpha.23.45 (accessed February 1, 2003).</p>

  <p style="margin: 5.0px 0.0px 2.0px 0.0px; font: 10.0px Lucida Grande; color: #808080">In-text, subsequent occurrence</p>

  <p style="margin: 0.0px 0.0px 0.0px 20.0px; text-indent: -20.0px; font: 12.0px Trebuchet MS">Smith and others, "Fractals," 943-949.</p>

  <p style="margin: 5.0px 0.0px 2.0px 0.0px; font: 10.0px Lucida Grande; color: #808080">Bibliography</p>

  <p style="margin: 0.0px 0.0px 0.0px 20.0px; text-indent: -20.0px; font: 12.0px Trebuchet MS">Smith, John Allen, Randall Benjamin Jones, Alfred Carlyle Black, and Susan D. White. "Fractals in Biological Systems." <i>J Biol Chem</i> 151, no. 22 (1999): doi:10.1006/ceth.2003.1354. http://www.jbiolchem.com/article/doi/10.1006/alpha.23.45 (accessed February 1, 2003).</p>

  <p style="font: 12.0px Helvetica; min-height: 14.0px"><br /></p>
</blockquote>
<p>Now it is much easier to be sure that citations will be formatted correctly in the different contexts in which they appear.</p>
<p>You can create as many of these preview contexts as you want, and they are created on a format-by-format basis because different formats care about different things.</p>]]>
        
    </content>
</entry>

<entry>
    <title>Using Conditional Elements: Example 2</title>
    <link rel="alternate" type="text/html" href="http://www.thirdstreetsoftware.com/blog/2008/08/using-conditional-elements-example-2.html" />
    <id>tag:www.thirdstreetsoftware.com,2008:/blog//1.9</id>

    <published>2008-08-22T17:41:03Z</published>
    <updated>2008-08-22T17:41:09Z</updated>

    <summary>Here is another example of how using conditional elements in bibliography definitions can save a lot of time, and produce better results than you are likely to get without them. In APA 5 (APA, Fifth Edition), like all of the...</summary>
    <author>
        <name>Michael</name>
        
    </author>
    
        <category term="Bibliographies" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Techniques" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.thirdstreetsoftware.com/blog/">
        <![CDATA[<p>Here is another example of how using conditional elements in bibliography definitions can save a lot of time, and produce better results than you are likely to get without them.</p>
<p>In APA 5 (APA, Fifth Edition), like all of the author-date formats, in-text citations typically look something like this: (Smith, 1997). But things get more complicated, depending on the details of the reference. For example, these are also valid in-text citations in APA 5:</p>
<ol>
  <li>(Smith, Jones, Black, White, and Grey, 1996) for the first occurrence of a reference, and</li>

  <li>(Smith et al., 1996) for the same reference in subsequent occurrences</li>

  <li>("Summer Solstice," 1972) when there are no authors for an article</li>

  <li>(<em>Western Slope Inns</em>, 1981) when there are no authors for a book</li>
</ol>
<p>There are many other variations, of course, but these will do for this example. Rather than talk about all of the details of APA in-text citations, I am going to focus on the use of different author list formats for the first and subsequent occurrences, and the substitution of titles for authors.</p>
<p>First, the rules for in-text citations are essentially the same for all reference types, so I created a component for the complete in-text citation that I then just use for all reference types. This means that I only have to get the details right in one place.</p>
<p>Next, just to keep things a little clearer in my head, I created a sub-component to handle the author names and titles. This component has four elements:</p>
<ul>
  <li>One Primary Contributors element (like an Authors element, but see elsewhere for more information) with the proper name formatting for the first occurrence of a reference in a document (e.g., up to 5 authors, then et al.). This element is set ti be used only under the condition that this is the first occurrence of the reference in the document.</li>

  <li>A second Primary Contributor, with the name formatting set up properly for all subsequent occurrences (e.g., up to two authors, followed by et al.), and dependent upon it not being the first occurrence.</li>

  <li>An Article Title element to be included only if there are no primary contributors, but there is an article title.</li>

  <li>A Publication Title to be included only if there are no primary contributors and no article title.</li>
</ul>
<p>That is really the core of the strategy. The component uses which ever version of the Primary Contributors element is appropriate in context (first occurrence or subsequent occurrence), and a fall-back cascade to use article title or publication title as appropriate if there are no primary contributors.</p>
<p>One side note, by using Primary Contributors instead of Authors, I automatically get whatever contributors are flagged as "primary." For most journal articles and books, this would be the authors. But for any reference where I have indicated that some other contributor should be considered "primary," those contributors will automatically be used both here in the in-text citation as well as in the bibliography. So when I decide to cite a particular recording by conductor rather than composer, the format automatically handles it for me.</p>
]]>
        
    </content>
</entry>

<entry>
    <title>Using Conditional Elements, Example 1</title>
    <link rel="alternate" type="text/html" href="http://www.thirdstreetsoftware.com/blog/2008/08/using-conditional-elements-example-1.html" />
    <id>tag:www.thirdstreetsoftware.com,2008:/blog//1.8</id>

    <published>2008-08-21T23:19:40Z</published>
    <updated>2008-08-22T04:33:19Z</updated>

    <summary>To help people who need to create or modify bibliography formats, I will be posting some examples of how to handle the complexities one actually encounters in real-world bibliography formats. Here is an example of how you can use conditional...</summary>
    <author>
        <name>Michael</name>
        
    </author>
    
        <category term="Bibliographies" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Techniques" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.thirdstreetsoftware.com/blog/">
        <![CDATA[<p>To help people who need to create or modify bibliography formats, I will be posting some examples of how to handle the complexities one actually encounters in real-world bibliography formats.</p>
<p>Here is an example of how you can use conditional elements when creating or modifying a bibliography format in Sente.</p>
<p>In Chicago 15 AD (author-date), the formatting of volume, issue and pages for a journal article can get a bit complicated. Here are some examples of how this information can appear (in each case below ABCD=journal, volume=12, issue=34, pages=56-78):</p>
<ol>
  <li><em>ABCD</em> 12:56-78.</li>

  <li><em>ABCD</em> 12 (34): 56-78.</li>

  <li><em>ABCD</em>, no. 34:56-78.</li>

  <li><em>ABCD</em> 12: doi:10.1006/berd.2006.2345.</li>

  <li><em>ABCD</em>, no. 34.</li>
</ol>There are a couple of interesting twists that make this format a bit tricky:

<ul>
  <li>there should not be a space after the colon, unless both volume and issue exist</li>

  <li>issue is formatted differently, and is separated from the journal name by a comma, if there is no volume</li>

  <li>page numbers are replaced by the DOI if there is one</li>
</ul>
<p>One way of implementing this using conditional elements would be to create a component and add the following elements to this component (in order):</p>
<ol>
  <li>Volume, with a prepended space</li>

  <li>Issue (prepend: " (" and append: ")"), if there is a volume</li>

  <li>Issue (prepend: ", no. " and append: nothing), if there is not a volume</li>

  <li>static text: ": " (colon with a space), if volume, issue and pages all exist</li>

  <li>static text: ":" (just a colon), if pages exist, and at least one of, but not both of, issue and volume exist</li>

  <li>pages (no prepend or append text), if there is no DOI</li>

  <li>DOI (no prepend or append text)</li>

  <li>static text "." without conditions</li>
</ol>
<p>This probably seems more complicated that it really is, and once this has been placed in a component, it can simply be used as a unit anywhere this is needed. And should you get it wrong in one detail or another, there is only one place where you would need to make the correction.</p>
<p>Now, you might be thinking that this all seems kind of complex, and you would be right. It is not as bad as it might seem, but it definitely is a bit complex. But the bottom line is that the Chicago format specification is complex, and this is about what it takes to handle it correctly.</p>
<p>As a point of comparison, I ran a few tests on a competing reference manager to see how it handles this very same format, and here is what I found for each of the examples above:</p>
<ol>
  <li><em>ABCD</em> 12 56-78. (space instead of colon)</li>

  <li><em>ABCD</em> 12 (34): 56-78. (correct)</li>

  <li><em>ABCD</em> (34): 56-78. (wrong issue format)</li>

  <li><em>ABCD</em> 12 56-78. (missing colon, no substitution of DOI)</li>

  <li><em>ABCD</em> (34): (wrong issue format, extra colon, missing period)</li>
</ol>
<p>I suspect that the format definition in this other software could be improved with a bit of tinkering (I was using the format as distributed with the product), but I wonder whether this software can be made to handle complexities like this.</p>
<p>Of course, Sente's built-in formats are not perfect, but we are committed to making them as accurate as we can, so we keep adding features that enable us to handle the remarkable complexities we find in the world of bibliography formats.</p>]]>
        
    </content>
</entry>

<entry>
    <title>Introducing Bibliography Format &quot;Components&quot;</title>
    <link rel="alternate" type="text/html" href="http://www.thirdstreetsoftware.com/blog/2008/08/introducing-components.html" />
    <id>tag:www.thirdstreetsoftware.com,2008:/blog//1.7</id>

    <published>2008-08-20T18:09:45Z</published>
    <updated>2008-08-20T18:41:24Z</updated>

    <summary>One of the most powerful new features in the bibliography format editor in Sente 5.6, is the ability to create and use &quot;components.&quot;Components are just like format specifications for any reference type, except that, once created, components can be used...</summary>
    <author>
        <name>Michael</name>
        
    </author>
    
        <category term="Bibliographies" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="Techniques" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.thirdstreetsoftware.com/blog/">
        <![CDATA[One of the most powerful new features in the bibliography format editor in Sente 5.6, is the ability to create and use "components."<div><br /></div><div>Components are just like format specifications for any reference type, except that, once created, components can be used in other format specifications just like the built-in elements.</div><div><br /></div><div>For example, most formats have a standard way of presenting publication details such as the name of the publisher, the place of publication and the year of publication.  In Chicago NB (Notes + Bibliography) it looks like this:</div><div><br /></div><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><span class="Apple-style-span" style="font-family: 'Trebuchet MS'; font-size: 12px; ">New York: Columbia Univ. Press, 1926.</span></blockquote><div><br /></div><div>The rule for even this rather simple set of information get a little complicated (e.g., how do you format it if you do not know the place of publication?), and the format is used for most reference types.</div><div><br /></div><div>In prior versions of Sente, you would have had to specify all of the rules each time you wanted this information to appear.  This was very tedious.</div><div><br /></div><div>In the new version of Sente, you can create a component called, say, "Publication Details" and simply include that component wherever you want this information to appear.</div><div><br /></div><div>Not only does this greatly speed up the creation of consistent formats, but should you find a problem in the definition of a component, all you need to do is to modify the component and the new version will be automatically used everywhere.</div><div><br /></div><div>It takes some time to figure out exactly what should be a component, but the new versions of APA, MLA and Chicago make extensive use of components, so you can look at the for some ideas about how components can be used.</div>]]>
        
    </content>
</entry>

<entry>
    <title>MLA 3: Why is &quot;Print.&quot; at the end of each entry?</title>
    <link rel="alternate" type="text/html" href="http://www.thirdstreetsoftware.com/blog/2008/08/mla-3-why-is-print-at-the-end-of-each-entry.html" />
    <id>tag:www.thirdstreetsoftware.com,2008:/blog//1.6</id>

    <published>2008-08-20T17:03:52Z</published>
    <updated>2008-08-21T20:41:52Z</updated>

    <summary>If you have used the new MLA style that we started shipping with Sente 5.6.5, you will have no doubt noticed that most of your bibliography entries end with &quot;Print.&quot; and I&apos;ll bet that many of you have wondered why...</summary>
    <author>
        <name>Michael</name>
        
    </author>
    
        <category term="Bibliographies" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="MLA" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.thirdstreetsoftware.com/blog/">
        <![CDATA[If you have used the new MLA style that we started shipping with Sente 5.6.5, you will have no doubt noticed that most of your bibliography entries end with "Print." and I'll bet that many of you have wondered why this is there.<div><br /></div><div>Here is an example:</div><div><br /></div><div><p style="margin: 0.0px 0.0px 0.0px 20.0px; text-indent: -20.0px; font: 12.0px Trebuchet MS">Gerber, Alan S., and Donald P. Green. "Social Pressure and Voter Turnout: Evidence From a Large-Scale Field Experiment."<i> American Political Science Review </i>102 (2008): 33-48. Print.</p><div><br /></div><div>This new version of MLA is based on the recently-released <span class="Apple-style-span" style="font-style: italic;">MLA Style Manual and Guide to Scholarly Publishing, 3rd Edition</span>. This new version of the book updates the MLA style to better indicate exactly what version of an article, book, etc. was consulted during research.  If you retrieved a PDF of the above article from JSTOR, the bibliography entry would look like this:</div><div><br /></div><div><p style="margin: 0.0px 0.0px 0.0px 20.0px; text-indent: -20.0px; font: 12.0px Trebuchet MS">Gerber, Alan S., and Donald P. Green. "Social Pressure and Voter Turnout: Evidence From a Large-Scale Field Experiment."<i> American Political Science Review </i>102 (2008): 33-48.<i> JSTOR. </i>Web. 13 Jan. 2008</p></div><div><br /></div><div>To support this, we added a new field in Sente 5.6.5 called "Web data source."  In the case above, this field should be populated with "JSTOR" and the Date Retrieved filled in appropriately, and the output would change to what you see above.</div><div><br /></div><div>For more information on this change to the MLA style, see Section 6.7 in the MLA Style Manual.</div><div><br /></div><div><p style="text-align: left;margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 20px; text-indent: -20px; font: normal normal normal 12px/normal 'Trebuchet MS'; "><br /></p></div></div>]]>
        
    </content>
</entry>

</feed>
