Import from AviSys, how-to

Bird Journal has direct support for importing AviSys records.

To get started, first export your AviSys records:
  • Open AviSys
  • Select "List Records" from the menu bar at the top of the page
  • Select "Normal" then click "List". It's preferable to import all records at once, as you'll only need to resolve species and locations once for all sightings.
  • Select "Date" for the sequence then click "OK"
  • Select "Export"
  • Select "Comma Delimited ASCII File" when prompted
  • You will be prompted with three Yes/No confirmation boxes for sighting attributes, expanding sighting places and shorter date format. Click Yes for the first two and set shorter date format to No.
Save the exported file somewhere convenient like your desktop. Then we can import this into Bird Journal:
  • Install the "AviSys Record Format" "Clements Taxonomy" from the Bird Journal library. Press the Library button on the menu bar, filter to Record Formats and Taxonomies to find them more quickly.
  • Import your data, by pressing the Tools button, then selecting Import.
  • Make sure the AviSys Record Format is selected, then browse to locate the exported file and press the Next button. You'll also want to make sure you have your preferred taxonomy selected on this screen. Bird Journal will use this taxonomy first when choosing which species to use.
  • Match all unmatched items, referring to this article if helpful.
  • Press Import when done.
Notes about the import from AviSys:
  • Unlike AviSys, Bird Journal does not require a count value to be specified. Import from AviSys leaves counts of one as unspecified to more accurately capture the level of detail recorded.
  • Bird Journal has the concept of an Entry as a collection of related observations. This means you can for example, enter notes for an entry *or* an observation, avoiding repetition of eg. weather or habitat information on each observation. AviSys notes are only given to individual sightings. Bird Journal will import these notes to each observation, ensuring no detail is lost. It will however lead to some visible repetition, where the detail is really related to the Entry (collection of observations).
  • AviSys properties are not currently imported, though are still present as codes in notes.
  • Locations are created, though not the full hierarchy. You can use the edit locations screen (accessed via the Locations button in the menu bar) to add additional locations and organize the hierarchy.
Troubleshooting:

AviSys location codes do not always follow the ISO-3166-2 standard used by Bird Journal, so cannot be auto-matched.  They will appear in the list of unmatched items.  Here's a list of the most common differences for your reference.
  • UH - Hawaii, not a country. Set to US.
  • ZB - Azerbaijan.  Set to AZ, following ISO-3166-2.
  • ZR - Zaire, now Congo, the Democratic Republic of the.  Set to CD.
  • IB - Borneo, covers Indonesia, Malaysia and Brunei and is not currently represented independently in Bird Journal. We have plans to support this. Set to Indonesia (ID), Brunei (BN) or Malaysia (MY) as appropriate.
  • SW - Sulawesi, not a country. Set to Indonesia (ID).
  • ZT, ZO - Ocean near Antarctica.  Set to Antarctica (AQ).
  • AA - Antarctica.  Set to AQ, following ISO-3166-2.
  • RZ - Rodriguez, not a country.  Set to Philippines (PH).
  • CS - Moluccas, not a country.  Set to Indonesia (ID).
  • LN - Lithuania.  Set to LT, following ISO-3166-2.
  • SS - Not a country (Timor, Roti).  Set to Indonesia (ID).

Feedback and Knowledge Base