|New! For another source for help and ideas, check out the Recollector Forum. This new forum has been set up so that you can pose questions and find answers, provide ideas and suggestions to others, and share your experience with the community of Recollector users.|
FAQ (frequently asked questions)
- Can I have more than one collection database?
- Is there a limit to the number of records in a collection?
- Is there a limit to the number of characters in a text field?
- Are there any restrictions on the fields that I can add to my collection database?
- Why are there three text data types? What are the differences among them?
- Can I modify the field definitions of my collection after I have begun to add data records?
- I made some errors while adding or editing data. How can I undo my changes?
- Can I make changes to my collection outside of Recollector, by editing the collection file in a text editor?
- Can I store my collection in the cloud?
- How can I move my collection to a different location or to a different computer?
- Can I move Recollector and my collection to a thumb drive, so I can run Recollector on different PCs?
- How can I delete a collection? (I was just testing out Recollector and made a “pretend” collection, but now it shows up in the list of my collections, but I just want it to go away.)
- Will my collection be lost when I upgrade to the next edition of Recollector?
- I added a jump-to link. It shows up OK (as a blue, underlined link), but when I click on it nothing happens. Why?
- What is the difference between Recollector's Product Version Number and its Collection Version Number?
Can I have more than one collection database?
Yes, you can have as many different collections as you want. Recollector keeps track of each new collection that you create in a separate file. You can have multiple collections open at once; each will be shown in its own collection window.
Each collection is completely independent of the others, so you can set up each collection with whatever choices are appropriate (fields to use, currency and dimension units choice, sorting order, etc.).Is there a limit to the number of records in a collection?
No. There is no limit to the number of records in a Recollector collection. However, keep in mind that Recollector keeps the current collection entirely in memory when it is opened, so if your collection is really huge, then it may take a while to read the collection into memory or to write it back out. Ultimately, there is some size limit that is imposed by the amount of physical and virtual memory that your computer has, but on any reasonably configured modern-day PC or Mac, you are very unlikely to approach that limit with data from a personal collection.
Testing has been done with collections containing over 10,000 records. These collections were read in or written out in just a couple of seconds, and once in memory there is no slowdown related to the size of the collection.
It is good to keep in mind that the amount of computer memory used by your collection is affected by the total amount of data, rather than by the number of records. So a 1,000 record database could be larger than a 10,000 record database, if the former contained much more data per record than the latter.Is there a limit to the number of characters in a text field?
No. You can have as much text as you want in a single text field. Obviously, if you want to make it easy to enter and edit lengthy text values in these fields, you should use the "long text" data type when defining the field. However, even short text and one-line text fields have no upper limit to their length (even though it is inconvenient to type in very long values in the single-line text-entry boxes that short text and one-line text fields use in the data-entry/editing window).
One of the formatting features designed for lengthy texts is the ability to have the text formatted (in the Item Details view) as multiple paragraphs. This is achieved, when adding or editing data, by including a single blank line where you want a paragraph break to be shown. The single blank line will be interpreted as a paragraph break, and the text will be formatted, in the Item Details view, into separate paragraphs.Are there any restrictions on the fields that I can add to my collection database?
Not really. When you initially create a collection database, you choose from one of the available templates, which provides you with a starting set of fields. But this is really just a convenience, so that some of the fields that you will have in your collection database will be there right from the start, without your having to individually specify them. But you are free to add any additional fields that you want (or modify or delete any of the fields provided by the template). There is no limit to the number of fields that a collection can have (though, of course, if your collection has hundreds of fields, you will likely find it somewhat cumbersome to edit and view your collection entries). The only restrictions regarding fields are these:
- Your collection must have an ID # field (though you are free to change its name, and you are free to never actually put any data into this field, if you don’t want to use it).
- Each field must be of one of the eight provided data types; you cannot create new data types.
- Each field has a name, and field names must be distinct within any single collection. Field names can be multi-word (for example: Acquistion date).
Why are there three text data types? What are the differences among them?
The three text data types (short text, one-line text, and multi-line text) are all used to hold text data, and in most respects these three field types behave identically. However, in the data-entry/editing window these three text field types are handled differently:
- As its name implies, a short text field is intended to be used for text values that are short: a few words or a short phrase, and the space provided in the data-entry/editing window for such a field is a fairly small text-entry box. If you plan to associate a field with a picklist (so that the field displays as a drop-down list in the data-entry/editing window), it must be defined as a short text field.
- A one-line text field is intended for longer text values, but ones that are still expected to fit on a single line. In the data-entry/editing window, the text-entry box (along with its label) for a one-line text field extends the full width of the window.
- A multi-line text field is intended for any field where you expect to have longer text values. Any field where you expect values to contain multiple sentences or multiple paragraphs should definitely be defined as a multi-line text field. Only multi-line text fields can be edited in separate, larger editing windows (by requesting this from the field's options menu)
Other than these data-entry/editing differences, all three text data types are the same. They are all used to hold text (of any length), they all can contain formatted text (bold, italics, etc.), jump-to links or any of the special hyperlinks supported by Recollector. Remember that you can change the data type of a field at any time. So if you have a field that you defined as a short text, but you find that in the data-entry/editing window the actual values you are entering are longer than what conveniently fits, choose Modify Fields or Image Directory from the Edit menu and change the data type for this field to be a one-line text field (or multi-line text field, if needed). See the next FAQ for more information on changing field definitions.Can I modify the field definitions of my collection after I have begun to add data records?
Yes. The "schema" of your collection database is not set in stone, and you can make changes to it at any time. Choose Modify Fields or Image Directory from the Edit menu of the collection window. (If you are using the Windows version of Recollector, you will be warned that the program will close the currently open collection before it can make modifications to its fields. The collection window will be automatically re-opened when you have finished making changes to your field definitions.) The Modify Fields dialog lets you change your field definitions: You can add, rename, change type, or delete fields. (If you delete fields you will be warned that any current data present in a deleted field will be lost when the collection is written out.)
In addition to modifying fields, you can change a collection's name, modify its currency or dimension units, or specify (or modify or delete) the Image Directory definition for your collection. These are all changes that can be made at any time, not just when you are initially creating your collection database.I made some errors while adding or editing data. How can I undo my changes?
The Windows and Macintosh versions of Recollector handle undoing and reverting changes somewhat differently.
Undoing changes in the Windows version:
Recollector does not have an “Undo” menu choice. (Text entry fields in the data editing window do have Undo/Redo choices on their right-click options menu; so you can undo just-performed typing or editing operations. You can also use Ctrl-Y or Ctrl-Z as keyboard shortcuts for Undo/Redo.) However, you can use Revert, on the File menu, to undo all the changes you made since the last time you saved your collection to disk in the current session. (If your collection has not yet been saved to disk in the current session, Revert will restore the collection to the state it was in when you began the current session.)
If you have saved your collection to disk in the current session, Revert will give you the choice of throwing away the changes made since the last save or all the changes in the current session.
In general, it is a good idea to do fairly frequent saves (Save, on the File menu) when you are making lots of changes to your collection (editing or adding new records). That way, if you realize that you just made a mistake, doing a Revert will only throw away the changes made since the last save, and you will probably only have to re-do a small amount of work, if any. To guarantee that changes are saved to disk on a timely basis, you can turn on auto-save from the Preferences dialog. Choose Preferences from the Options menu and select the Auto-save tab. Pick Auto-save and select an auto-save interval.
If things get a bit more desperate, and you realize that you have made a number of mistakes, and you saved the collection to disk with mistakes present, you can always choose to Revert to the state of the collection as of the beginning of the session. You will have to re-do this session’s work, but at least you will have your collection in a state that excludes all the mistakes of the current session.
Undoing changes in the Macintosh version:
During editing, you can use Undo (or use the keyboard shortcut: ⌘Z) from the Edit menu to undo recent edits (typing, pasting, etc.). If you have made multiple changes during the editing of a single record, you can use Undo multiple times to back out of each of your changes.
If you have made changes to your collection which have not yet been saved to disk, the title bar of the collection window will show this by appending "Edited" to the collection name. To undo all edits since your collection was last saved, choose Revert Document from the File menu.
If you have not made any changes to your collection since it was last saved, you can still restore your collection to an earlier state by choosing Revert Document from the File menu. This will bring up the "Versions" display, in which the current state of the collection is shown on the left, and a stack of earlier versions is shown on the right, with a time scale at the right edge of the screen. You can scroll back through earlier versions and restore the collection from any of these earlier states.Can I make changes to my collection outside of Recollector, by editing the collection file in a text editor?
No and yes. (Read on.)
No, in the sense that if you edit the collection file outside of the Recollector environment, you risk corrupting the file in such a way that you may not be able to open the file the next time you try to do so with Recollector.
Yes, in the sense that the collection file is a text file, in XML format, which can be opened and modified by any text editor. In other words, there is nothing, physically, that prevents you from opening the collection file with, for example, notepad (on Windows) or TextEdit (on the Mac), and making changes.
If you want to make changes to your collection, the proper way do this is within the Recollector program, not outside of it by editing the collection file.
If you really feel compelled to edit the collection file directly (and you consider yourself a guru on XML file structure), you are obviously on your own. There are few good reasons, if any, why this should ever be necessary. At the least, you should make a backup copy of the collection file before making any changes to it, because in the likely case that the edited version can no longer be successfully opened by Recollector, at least you will be able to gracefully fall back to restoring the file to its prior state from the backup copy.Can I store my collection in the cloud?
Yes. Usually people store their collection data on their hard disk. But if you use one of the popular cloud-based file-sharing services (for example, Dropbox, Google Drive, OneDrive, iCloud Drive), you can store your collection data (including images) in the cloud. Not only does this protect your data against disk or computer failure, but it also makes it possible to access your collection from multiple computers. This is true whether it is just you, wanting to access your collection from both your home computer and your office computer, or you and a family member or colleague who want to work together on using and maintaining a collection. Learn how to do this here.How can I move my collection to a different location or to a different computer?
The best way to move a collection is with the Backup and the Copy capabilities of Recollector. This method guarantees that your collection, with its images intact, will be properly moved. The first step is to back up your collection, using Backup (on the Mac this menu item is named Backup Collection) off of the File menu. If your collection contains images (or audio or video clips), make sure to select Back up the collection file and all the image/audio/video files in the window that comes up. Also choose the parent directory for the backup. The backup process will create a sub-folder in this parent directory, whose name reflects the name of the collection and the date and time of the backup. For example, the folder created might be named BookCollection_23APR2012_11_25.
If you are moving your collection to a different computer, you should copy this entire backup folder to the other computer (for example, using a flash drive). You must, of course, have Recollector installed on the other computer in order to import the copy of your collection from the backup data. Note: You can move a collection between from a Windows to a Mac computer, or vice versa.
Pick Restore or Copy a Collection from Backup from the File menu. (On the PC version of Recollector, if the program starts up without displaying a collection window, then the Start-Up Windows will be shown. This window has a button to invoke the same task: Restore or Copy a Collection from Backup.) You will then be asked to identify the backup folder (the folder that was created in the backup step). Also, select the Copy the collection ... choice. (The Restore the collection ... choice is meant for the situation where you are restoring - to its original location - a lost or damaged file from backup.) After selecting Copy the collection, click the Browse button to choose the folder where the new collection will be created. The copy of the collection will be made to this folder, with a sub-folder named Images created for copies of the collection's image files. When the copy is complete, the newly copied collection will be opened.Can I move Recollector and my collection to a thumb drive, so I can run Recollector on different PCs?
Yes. Under MS/Windows, Recollector can be installed on a thumb drive, and your collection data (the collection file and any associated images) can all be put on the same thumb drive along with the program. This allows you to run Recollector on different computers by simply plugging the thumb drive into a PC's USB port and running the program from there. To do this, you need to install Recollector onto the thumb drive, using the steps described in the following document: Installing and Running the Windows version of Recollector on a USB Thumb Drive. This ability to run Recollector from a thumb drive is not available for the Mac. However, on a Mac you can choose to put your collection data (collection file and image files) onto a thumb drive (rather than on the hard disk).How can I delete a collection? (I was just testing out Recollector and made a “pretend” collection, but now it shows up in the list of my collections, but I just want it to go away.)
There is no menu choice for deleting a collection. A collection file is just a single file on your computer's hard drive, so simply use the Finder (on the Mac) or Windows Explorer (on the PC) to locate the collection file and move it to Trash or delete it. You should not have that collection open in Recollector when you delete it by eliminating the collection file. (Otherwise, Recollector is likely to re-create the file again when it closes the open collection.)
Deleting the collection file does not delete the associated image, audio or video files. If you want those to also be deleted, you should delete them in the same way (with the Finder on the Mac or Windows Explorer on the PC). If you have used an Image Directory with your collection, you can usually delete all of a collection's image/audio'/video files by simply deleting the Image Directory itself.Will my collection be lost when I upgrade to the next edition of Recollector?
No. When you move to the next edition of Recollector, nothing is changed with regard to your collection. Collection files contain version number information, and if a new version of Recollector, containing new features, needs to update your collection file, it will do this automatically. The only possible problem is using an older version of Recollector on a collection file that was created by a newer version of the program. Recollector, however, recognizes this situation and an older-version program won’t let you open a later-version collection file – an error message will be shown indicating this situation.I added a jump-to link. It shows up OK (as a blue, underlined link), but when I click on it nothing happens. Why?
There are three possible reasons why clicking on a jump-to link doesn't perform the expected jump:
- The ID # shown in the link doesn't exist in the collection. Make sure that you actually have a record with this ID # in your collection.
- You currently have a subset defined, and the record with the ID # that you are trying to jump to is not included in the current subset.
- The text that you selected to turn into a jump-to link has some extra characters that aren't part of the actual ID #. For example, if the text that you have made into a jump-to link is #123, but the actual ID # for the corresponding record is just 123 (without the leading '#' character), then the jump-to link won't work. Change the jump-to link to include just the characters that form the ID # value of the record that you are trying to link to. In the current example, leave the '#' character out when selecting the text to turn into a jump-to link.
What is the difference between Recollector's Product Version Number and its Collection Version Number?
The Product Version Number identifies the version of the program (Recollector). Every time a new feature, an enhancement, or a bug fix is added to Recollector, the Product Version Number is changed. This number is a three-part number (e.g. "2.6.2"). For most minor changes, the last component is bumped (e.g., going from 2.6.1 to 2.6.2). For more signficant changes, the middle part is bumped, and the third part is re-set to 1 (e.g., going from 2.5.13 to 2.6.1). When the entire program has been overhauled or reimplimented, the first part will get bumped, and the second and third parts will get re-set to 1 (e.g., going from 1.12.5 to 2.1.1).
The Collection Version Number refers to the structure and organization of the collection file (the XML file) used to save a collection's data to disk. The is a two part number (e.g. 1.5), and it is likely to always have a first part of "1" and only change in its second part. Collection Version numbers change much less frequently than Product Version numbers. The Collection Version Number is needed because sometimes a new feature is added to Recollector that involves adding or changing the way collection data is stored when saved to disk in an XML file. A given Product Version knows how to read a collection file encoded using the current Collection Version, and it also knows how to read older Collection Version files and convert them to the current Collection Version. But Recollector is not clairvoyant, and the current Product Version does not know how to read a file encoded using some future Collection Version. This situation can arise if a collection file is created with a new version of Recollector and then moved to a different computer where it is opened by an older version of Recollector. The program recognizes this situation and tells you that it cannot open the collection file, because the file uses an unsupported (i.e. future) Collection Version. (The solution is simple: Upgrade the version of Recollector to the latest version; then you will be able to open the new collection file.)
Check out the Recollector Forum, to pose questions, find answers, and share your experiences with other Recollector users.
Access the Recollector User's Guide from the Help menu of Recollector. The User's Guide is also available online:
Training videos are available that show you how to get the most out of Recollector.
TECHNICAL SUPPORT CONTACT INFORMATION
If you can't still can't find the answer to your question about Recollector, please contact MapRecord Publications: