OOo Off-the-Wall: Back to School with Bibliographies
A bibliography, also known as "Works Cited" or "Reference List", is a list of sources for ideas contained in a document. Typically, the list is accompanied by citations, brief references within the body of the document, that direct readers to detailed information in the list. Depending on the format used, both the sources of ideas and of direct quotations may be used in a bibliography.
Bibliographies are used commonly in academic or research papers. In that form, they are considered to be not only proof of honesty but also an acknowledgment of the author's intellectual debt to others.
Whether you are using the Chicago, Modern Languages Association or American Psychiatric Association style for bibliographies and citations, OOo Writer's bibliography tools are flexible enough to handle your needs. However, the process of creating the bibliography is confused by two things. For one, bibliographies are lumped together with indexes and tables of contents. Second, OOo Writer provides misleading samples for its bibliography database. For this reason, it is worth walking through the process step by step to avoid confusion.
Information for Writer bibliographies may be stored in a database. There is a single database for each user of OpenOffice.org on the system. Called biblio.odb, it is located in the /.openoffice.org2/user/database folder in each user's home directory. It is based on the file of the same name in the /presets/database directory of the main installation in the /opt directory. When assembling a bibliography, you have the option of using this database or of storing bibliographic information within the current document.
Within a document, bibliographies consist of two parts:
The list of works at the end of a document. This list can be built by using records in the bibliographic database for the document or from records created when a text citation is entered.
The citations within the text of the document. These citations guide readers to the complete reference in the list at the end of the document. In Writer, they are made from the Short Name (Identifier) for a record. They are roughly equivalent to the entry markers used for other tables and indexes, but they are only one field in a database that has additional entries.
Writer's database includes sample entries. Unfortunately, these samples need to be replaced, because they confuse more than they help. They are misleading or incomplete in several ways:
The Identifier, which is called the Short Name in Insert > Indexes and Tables > Bibliography Entry, is the content for the text citation or bibliographic entries. However, the sample entries use a meaningless code that is useless for citations unless they are changed.
The fact that which fields you need depends on the bibliographical style and the type of source you are using is obscured by the fact that all the samples are books. In fact, in any given record, many of the fields are going to be blank.
The samples use the fields incorrectly even for books. For example, they use the Title column, which is supposed to be for articles and shorter works, rather than the book column. Similarly, they use the Page field to list the number of pages in each book. In fact, the field is intended to list either the starting page or the range of pages covered by an article or smaller work. These errors could cause false results if you were searching for information.
These errors are worth noting, because you might spent long minutes puzzling how to apply the example of the samples. You can't, so delete the samples instead of wasting your time.
To add or edit a bibliographic database:
1. Select Tools > Bibliography Database. The bibliography database opens. Sample records are included.
2. If you are editing an existing database, use several buttons on the toolbar to help you find a record to edit:
The Autofilter arranges rows in alphabetical or numeric order according to the column you select. Using Author is often the most useful filter.
The Standard filter allows you to set custom filters based on the column, the condition and the value. For example, if you set the filter to Type=14, only unpublished sources would show.
The Remove filter button returns the display to the default setting of showing all records.
The Column Layout button sets the order of columns, starting from the left side of the table.
Each column head has a right-click menu that you can use to Hide the column to simplify the table. You can unhide columns by selecting Show Columns from any other column head.
3. Do one of the following:
To add a new record, select Insert > Record. A new row is added to the table. It has an arrow in the row header.
To edit an existing record, click anywhere on its row. The currently selected row is listed in the status bar of the database table.
The easiest place to add or edit information for a record is in the fields at the bottom of the screen. The fields correspond to the tables at the top of the screen.
You do not need to fill in all of the available screens. Instead, enter only the definitions you require for the form of citation you are using. A book, for example, requires different fields from a magazine article or an Internet site. Consult a guide to the bibliographical style that you are using for information about exactly what information each type of article needs.
Remember that each record must have:
A Short Name, called the Identifier in the database table. This field is the content for any text citations to the record. The structure for this field depends on the citation style and the type of record you are using.
A Type, such as book or unpublished.
For most citation formats, you also need to enter the Author, Book Title or Title for an article or shorter work, year of publication and the publisher. In some cases, you also may want to use one of the User-Defined fields for the city.
4. Add or edit any other records.
You do not need to worry about the order of records as you enter new ones. When you are finished, you can use the Autofilter button to arrange them in the order you prefer.
5. When you finish, close the bibliographic database window.
You do not need to save the database with a command. It is saved automatically when closed.
-- Bruce Byfield (nanday)
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Tech Tip: Really Simple HTTP Server with Python
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Returning Values from Bash Functions
- Rogue Wave Software's Zend Server
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide