Jan 04, 2018 Is DB Text Secure? Smrogers: 0: 74: about Sets: jpcarre: 4: 654:. Www.Inmagic.com Inmagic Forums Inmagic Forums DB/Textworks. Contact Us www.Inmagic.com. Welcome to Inmagic® DB/TextWorks®! This manual contains procedural and reference information, including instructions about how to use the software.

Quick Links • • An Introduction to DB/TextWorks This database software allows you to create surrogates for the items in a collection. It was designed by librarians and is used in many libraries for their online catalogs (for instance, the Pala Tribal Library in San Diego County and the collection of the U.S. Federal Reserve Bank) and for other databases. We use it for LIBR 202 because it combines a database structure with the ability to do text retrieval within the database fields. It instantiates the information storage and retrieval concepts that we cover in this class.

Database design has two fundamental steps. The first is to determine what the data structure should be, based on your knowledge of the collection, the users, and principles of information retrieval. The second is to create the actual records (surrogates) for the entities in the collection.

The records are the part of the database that contain the information about each object in the collection; the data structure is the format for the records. A very simple example of these two steps: Say you wanted to design a database for your collection of 1960s LP records. The first step is to determine what the data structure should be, based on your knowledge of the collection, the users, and principles of information retrieval. To begin with, every record should have a unique identifier that refers to one specific object in the collection - this can be a simple number starting with 1, progressing up to 20 or 2,000 or whatever. The less simple decisions concern how people will want to aggregate the items in your collection.

Gratis Style Dangdut Yamaha Psr S700. Will they want to find all the records released in a given year? Will they want to find all the records from a particular musical genre?

Will they want to find all the records by a particular artist? Will they want to find all the records with female/male/group vocalists? If the answer to all those questions is 'yes,' then your data structure will need to have fields for Year Released, Genre, Artist, and Vocalist.

After you've decided on the fields, you need to decide how to format what is put into the field - for instance, should year of release be expressed as 1963 or 63? Will you distinguish folk from folk rock under genre, or group them together? Will you use the name John Lee Hooker, or John Hooker, or John L. Hooker for the blues artist? Will you use the Motown term 'girl groups' in the Vocalist field or 'female vocalists'? Detailed decisions have to be made about the values which you will allow for each field. For some fields you will need to standardize the choices as this paragraph suggests; for other fields you may just take whatever information the album cover or liner notes provide.

So in this example, your fields will be: unique identifier, genre, artist, vocalist, and you may also want album title and titles of individual songs on the album. For each field, you'll need to decide how to express the information about the albums so that it's consistent and predictable. If you want to limit the terms that can be used for some of the fields to certain values that you specify ahead of time, you'll create a validation list for that field as part of the data structure. Once you have made firm decisions about the fields and values and put them into your data structure, you go to step 2 and create the actual records, one record for each item in your collection.