Encoded Archival Description (EAD) Export for DB/TextWorks

by Jonathan Jacobsen Wednesday, April 28, 2010 3:49 PM

In collaboration with Artefactual Systems, Andornot has developed an Encoded Archival Description (EAD) export report that can be used with our Archives Online textbases, or other, similar Inmagic DB/TextWorks archival databases.

EAD is an XML standard for encoding archival finding aids, maintained by the US Library of Congress in partnership with the Society of American Archivists.

The DB/TextWorks EAD export report was developed specifically for use by British Columbia archives to contribute detailed archival descriptions (to the item level) to MemoryBC, the province-wide online archival repository operated by the Archives Association of British Columbia.

The EAD XML export report is included with the latest version of Archives Online, but is also available as an exported textbase form that can be imported into any existing Inmagic DB/TextWorks database. Some adjustment of the form will be required for earlier versions of Archives Online and other databases.

To use the EAD export, you would:

1. import the EAD report into your textbase and adjust to match your fields if necessary;

2. search for one or more fonds and view the results with the EAD_XML report; and

3. write the report to a file with a ".xml" extension (e.g. myfonds.xml).

The XML file may be opened in a text editor such as Notepad to preview the results, then uploaded to another system, including MemoryBC.

The report is available at no charge by contacting Andornot (regular consulting fees will apply if you need any assistance with the report and export).

Tags: Archives | EAD

Printing Single Labels in Genie

by Jonathan Jacobsen Tuesday, April 06, 2010 1:43 PM

Many of our Genie clients have asked how they can print just one label for a book from the Genie catalogue when they have several Item records. Typically, when selecting a Catalogue record, adding it to the InfoCart, and printing labels, a label for each Item record is produced. This is fine when initially adding multiple copies of a work to your collection, but if you later add another copy, you really only need to print a label for that additional copy.

A sharp-eyed Genie user noticed this entry in the Genie Technical Notes (p. 33 of the Genie 3.3 version):

Attribute

Required

Default

Explanation

ItemCallNumberRequired

No

"false"

If set to "true", only the labels with nonempty ItemCallNumber field values will be printed.

"Ah-ha!" we said. "This could be the answer."

For this client, we edited the label report in MyLabels.config to add ItemCallNumberRequired="true" to the label definition, and ensured the ItemCallNumber field (rather than the CatCallNumber field) was on the spine label area of the label. Their existing Item Records don't have call numbers in the ItemCallNumber field, only the CatCallNumber field in the Catalogue record. As they add additional copies of works already in the Catalogue, they will enter a call number in the ItemCallNumber field. With the changes made to the label format, a label will be generated for just that one new copy. Brilliant! And with the Edit link added to the InfoCart (described in this blog post), they can quickly fix errors in records before printing the label.

This won't work quite as well for everyone though. If you already have call numbers in Item records, a label will still be generated for all of them. Nonetheless, it's good to have an option that can be adapted to other situations.

Making Inmagic Databases Accessible on the Mobile Web

by Jonathan Jacobsen Thursday, March 25, 2010 9:56 AM

blackberry_askme_demo It has been said by many that 2010 will truly be the year of the mobile app. BlackBerries have given remote access to email for years, and the iPhone has been one of the hottest selling phones since its launch. Many other devices now also come with built-in web browsers, fast internet access and large enough screens that accessing websites on a handheld device is almost as easy as on a desktop computer. Almost, but not quite. Full-size websites can be displayed on smaller devices, but viewing them typically requires a lot of scrolling around and zooming in and out. Websites optimized for mobile devices are still a great way to give the best user experience on handheld devices.

Fortunately, it's quite easy to make your Inmagic database accessible to mobile browsers, using WebPublisher Pro and a bit of elbow grease. We’ve just finished making a version of our Andornot Starter Kit (ASK) mobile-friendly. The ASK Mobile Edition is a set of search and results forms specifically designed for mobile devices. The layout is aimed at devices with a screen resolution of at least 240 pixels width, but doesn't require any more than that. Users may search by clicking pre-created links for popular searches, such as recent acquisitions, popular subjects or the latest journals received, as well as use a search screen to enter terms and select options using radio buttons and tickboxes. In all cases, the interface is designed not only for readability on smaller screens, but for selection of options with fingers, stylus and keyboards, depending on the device used to access it.

iphone_askme You can view the ASK Mobile Edition demo site here. If you'd like to see it as it appears on a mobile device, you can use the Opera Mini Java demo here. Just type ask.andornot.com/Mobile.html into the demo browser’s address bar to connect to the ASK Mobile Edition demo site.

This same approach can be taken with any Inmagic database and WebPublisher Pro, making search and results pages fit a smaller form factor. The effort to do so is not great – from half a day up to a couple of days for Andornot to help you.

The mobile web is all about making access even more convenient for users – allowing them to look something up the moment they think of it, wherever they are. The question is no longer "Why would someone want to search my database from their palm"; it's "Why wouldn’t they?" Don't get left behind as more users seek out mobile-friendly information. Contact us today to see how we can help put your databases in users' hands.

Using the Genie Orders Module as a Wish List

by Jonathan Jacobsen Wednesday, February 24, 2010 3:22 PM

The Genie Orders module can be used not only for tracking materials ordered, including books, journal subscriptions and standing orders, but as a wish list – a database of materials you are thinking of ordering, or that have been requested by your users.

To use the Orders Module as a wish list, we recommend editing the Order Types listed in the MyGenie.config file to add a wish list entry.

e.g. <Type>Wish List</Type>

When entering order records, select this order type and optionally use the Requestor field to record who wished for the item. You will not likely want to create a Catalog record for these Order records just yet – not until you actually order them.

You may wish to edit the Orders Search screen to be able to search for items on the wish list. To do so, open MyQueries.config and find the "orders_search" search screen. The simplest way to add a new field is to copy en existing one and change the field name to OrdType.

e.g.

<QueryField Type="QueryField" CssClass="SearchTextInput" LabelCssClass="SearchLabel" ShowBrowse="true" ShowBoolean="true" FieldList="OrdType"/>

This will allow you to find all items on the wish list. When enough have accumulated, you might select them from the search results and email the list to staff for a vote in which ones to actually order.

Using the Genie InfoCart to Edit Catalog Records

by Jonathan Jacobsen Monday, February 22, 2010 11:40 AM

The Catalog InfoCart feature in Genie is a handy way of collecting records that you want to edit. As you search through the Catalog, you can click the Add to Cart link without interrupting your searching. When you have assembled a collection of records to edit, you can view the InfoCart, and by making the small change described below, click an Edit link within the InfoCart display to edit each record. The Prev and Next links on the Catalog edit screen will take you through the records in your collection, without having to either return to the InfoCart or search for the records again. This is a great workflow improvement.

To enable the Edit link in the InfoCart, open the MyReports.config file in a text editor and find the "InfoCartBrief" report. If you haven’t made any other changes, the final 2 lines of the report definition will look like this:

<Field Header="&lt;br/&gt;&lt;br/&gt;">%%CartRemove</Field>

<Field Display="&lt;br/&gt;&lt;br/&gt;">%%Label</Field>

which displays the Remove from Cart link.

If you change the above 2 lines to these:

<Field Header="&lt;br/&gt;&lt;br/&gt;">%%EditButton</Field>

<Field>%%VerticalBar</Field>

<Field>%%CartRemove</Field>

<Field Display="&lt;br/&gt;&lt;br/&gt;">%%Label</Field>

the InfoCart will display an Edit link and the Remove from Cart link, separated by a |.

After saving the config file, be sure to reload it by selecting the About Genie link in the Genie menu and clicking Reset.

Month List