CSV or Comma Separated Value files - These files contain the data for each database column separated by a comma. The first line of the file is a mapping line which allows you to map the data to ReaderwareAW database column names.
TAB Delimited Files - These are similar to CSV files except that the data is separated by the tab character. Again the first line of the file is a mapping line which allows you to map the data to ReaderwareAW database column names.
"Title","Artist","Publisher"The problem is how does ReaderwareAW know what order the columns are in? The mapping line is key to importing data into ReaderwareAW. The first row of the file is the mapping line and it identifies which ReaderwareAW database columns the data should be imported into. This is a common technique used with CSV and TAB delimited files, your file may already have a mapping line as the first line of the file. or it may just contain the data. You need to open the file using a text editor like Notepad or TextEdit. Look at the first line. If there is a mapping line, you need to change the column names to match the ReaderwareAW column names. If it is not there, you need to add the line.
"Faith and Courage","Sinead O'Connor","Atlantic"
|ReaderwareAW Column Names|
|Artist||Artist or group|
|Title||Album title, required|
|LCCN||LCCN - Library of Congress Card Catalog Number|
|Dewey||Dewey Decimal Number|
|Call_Number||Library of Congress Call Number|
|User_Number||Used for your own numbering system|
|Catalog_Number||Label catalog number|
|Barcode||The raw barcode|
|Release_date||Date of publication|
|Running_Time||Album running time|
|Copies||Number of copies of this album|
|Format||Hardcover, Paperback etc.|
|Sound||Sound, Mono, Stereo etc.|
|Item_Condition||Condition of the album|
|Cover_Condition||Condition of the album jacket|
|Category1 - Category3||Album categories, ReaderwareAW supports up to 3 categories|
|Keywords||Album related keywords separated by commas. 255 characters maximum|
|Product_Info||Album information, synopsis, reviews etc. 65536 characters maximum|
|My_Comments||Your comments on this album. 65536 characters maximum|
|Favorite||Favorite album? True or False|
|Playlist||Include in playlist? True or False|
|Played_Count||Number of times you have played this album|
|Last_Played_Date||Last time you played this album|
|Recording_type||Type of recording, Studio, Live etc.|
|Recording_date||Date of recording|
|Location||Physical location of this album|
|Weight||Shipping weight of this album|
|Source||The source of the information, i.e. web site it was cataloged from|
|Item_Value||Current value of this album|
|Valuation_Date||Date this album was last valued|
|List_Price||List price of album|
|Purchase_Price||Amount paid for the album|
|Purchase_Date||Date this album was purchased|
|Purchase_Place||Where this album was purchased|
|Out_Of_Print||Out of print? True or False|
|Currency_symbol||Currency symbol used for all prices|
|Media_URL||Link to related media, e.g. MP3 file|
|Owner||Owner of this album|
|Status||Status, must be one of Own, Want, Ordered, For Sale, Sold, Withdrawn, Missing|
|External_ID||External ID for this album|
|New_Value||Value of a new copy|
|New_Count||Number of new copies available|
|Used_Value||Value of a used copy|
|Used_Count||Number of used copies available|
|Collectible_Value||Value of a collectible copy|
|Collectible_Count||Number of collectible copies available|
|Buyer_Waiting||Buyer waiting for a copy of this album|
|Sales_Rank||Sales ranking of this album|
|User1 - User10||User defined fields. ReaderwareAW supports up to 10 user defined fields. Maximum length 255 characters|
Automatic detection - In most cases Readerware can determine the encoding by examining the file. This is the default selection and you should normally use this and only specify an explicit encoding if there is a problem.In general you should use automatic detection. If Readerware is unable to determine the encoding used, you can select the correct encoding from the list.
ANSI - This is your system encoding and is the default. It will work for databases that contain the system language.
Unicode (little endian) - Unicode is a double byte character set and can handle virtually any language and any combination of languages. Little endian is used on Intel systems.
Unicode (big endian) - Unicode is a double byte character set and can handle virtually any language and any combination of languages. Big endian is used on other systems like PPC.
UTF-8 - UTF-8 is a variable width encoding and can handle all characters in the Unicode character set. It has become popular as you don't need to worry about endianness.