The following provides some useful tips on using Heurist.
1. Organise your record types
Use the tabs at the top of the record-type management screen to organise your record types into logical groups, and place your most frequently used group as the first tab (tabs can be dragged left and right, tab labels can be edited and new tabs created). Tab groups and ordering affect the order in which record types appear in pulldowns. A small investment in well-organised groups will make it much easier to pick from lists or find record types when you need to make changes.
2. Pay attention to section headings, field order, field widths, requirements and description
The few extra minutes you will spend ordering the fields in each record type, splitting them up into sections with section headers, and setting the basic parameters of requirement, repeatability and field width, will make all the difference to ease of data entry and the way you—and other users—feel about entering data.
3. Document your database
Don’t cop out on writing proper help texts and descriptions of record types, fields and terms, even if you are the only person using the database. A few extra minutes spent writing an explanation of the content of each field will ensure that the database is still interpretable way into the future, by you or by others if deposited in an archive (your descriptions automatically become part of the archive package). Do it as you are setting up the database, because you will never come back to do it later …
Heurist makes it easy to model your data. Start by identifying all the entities which make up your domain: people, organisations, cultural groups, places, events, documents, images, albums, series, compositions/movements, plays/acts/scenes. Pay particular attention to defining component parts or variants which may need a specific set of descriptors (attributes) such as instances of education or service (described by institution, degree, unit, rank, dates etc.) or variant attributes for different types of event or object.
5. Create some saved searches
Saved searches are the key to setting up useful ‘views’ of your data. Use them to quickly navigate to the records you are working on, to produce sorted lists, to publish sets of data to a web site, to organise the data which have been entered or imported in no particular order. Saved searches not only define a subset of your data and its ordering, but can also set up the way it is presented (e.g. as a map, a formatted report or a visualisation of related records).
6. Use record pointer and relationship marker fields
Record pointers are the workhorse for quickly and easily building simple relationships between records. Use a record pointer field to establish a hierarchical relationship through a pointer to a parent record (e.g. a chapter belonging to a book or a photograph belonging to a collection) or to indicate records with a specific role in relation to the entity being described (e.g. the author of a book, the producer of a film, the venue where a play is performed, a birth or commemoration event, a qualification).
Relationship markers are similar to pointers but carry additional information; minimally, a relationship type, but also commonly a date range over which the relationship is applicable. Relationships are useful where there are lots of potential types of relationship (e.g. roles that people may play in relation to a theatre production), as an alternative to defining a separate pointer field for each role. They are also useful where the relationship has a limited duration (e.g. relationships of employment, patronage, residence or exhibition/loan).
As a general rule, use a pointer field, constrained to a specific record type (e.g. place, person, series, component), where you will record a single value (e.g. parent) or a small number of values (e.g. authors) which have an unequivocal relationship with the entity being described and where multiple pointers are all equivalent (although they may be ordered—authors being a good example). Use a relationship marker field where you do not know a priori which relationships will be present and/or there are numerous possible relationship types, or the relationships have a temporal range, or the relationships are subject to interpretation and you need to provide supporting information through notes or references.
7. Invest in writing some report formats
A database is useless if you can’t get data out of it. Heurist has several pre-defined output formats, but you will get much more from it if you write your own using the Report tab on the search interface. Although a little tricky to get started with, the report formatter is extremely powerful and can generate everything from a data stream for input to an analysis package to beautifully formatted output embedded in a web site.
8. Use the delimited import to merge data