A new menu on the catalogue media list view allows new controls.
This allows you to export information about the current found set of media to a variety of file formats. Choosing an unpassworded “.fmp12” file will output images and associated data into a self contained file.
Will export the raw images to a new folder on your computer’s desktop (assuming you have privileges to save files there).
Will loop through the images and attempt to rename the stored images:
if the image is linked to an ISBN, Athenaeum will attempt to rename the image to the ISBN (e.g. untitled.jpg might become 0006483356.jpg). If an image with that name already exists a number is appended to the name (e.g. 0006483356–2.jpg)
if there is no ISBN, then Athenaeum will attempt to rename the image using the bar code of the image.
Renaming images can make it easier to re-link them at a later date should you move your data.
When using windows and pasting images - say from a web page - into Athenaeum, two minor issues can arise:
the image has no name so simply is named untitled-x.bmp (where “x” is some unique number)
the image is normally pasted as an inefficient .bmp (windows bitmap image).
This function will firstly attempt to rename the untitled images in a logical way.
Secondly, it will discard the inefficient .bmp image, leaving behind a compressed .jpg image. The space saving when doing this is signficant, typically reducing storage requirements for images by 90 or 95% with no apparent loss of image quality. Repeating this action on thousands of .bmp images will significantly lighten the load on servers and their backups.
Over time, it is possible that items deleted from the catalogue and possibly removed from the archive can leave behind the catalogue images (and other types of documents) stored in the catalogue media (containers) table.
This function will list such items. You might export the images to a folder on the desktop (use the Export Found Set to a Folder option) and then delete the records in bulk or individually.
Images/containers that are not linked to the catalogue nor archive show a yellow warning to the right.
“Containers” such as images, movies, pdfs, word processing documents, etc. that you may add to the catalogue are stored external to the Athenaeum databases.
Athenaeum Pro 2017 consolidates the locations of these to make it a bit easier for IT staff to manage, as they are occasionally want to do.
Four of the Athenaeum Pro data files have externally stored container data. For example, the book cover images are stored in the media folder, which is part of ap_catalog.fmp12. When running Athenaeum Pro locally, all of the folders are stored inside the “athpro_data” folder.
tech note: When running Athenaeum Pro on FileMaker Server, an additional two levels of folder heirarchy are introduced. This is because FileMaker Server will try an open FileMaker files up to two levels deep in the standard data folder and it is possible to store FileMaker files into container fields, so it is important that FileMaker Server does not try to open these.
All external data (remote container data) contained within their respective folders inside the “athpro_data” folder.
ap_AthenaeumPro.fmp12 ap_barcode.fmp12 ap_borrower.fmp12 ap_catalog.fmp12 ap_circulation.fmp12 ap_circulationarchive.fmp12 ap_MARC.fmp12 ap_photo.fmp12 ap_web.fmp12 📂 athpro_data 📂 alert 📂 background 📂 barcodefont 📂 location 📂 logo 📂 marc_image 📂 media 📂 photo 📂 qr 📂 switch 📂 type ISBN collection utility.fmp12
FileMaker Server requires an additional two levels of folder structure: RC_Data_FMS->file name->container folder.
ap_AthenaeumPro.fmp12 ap_barcode.fmp12 ap_borrower.fmp12 ap_catalog.fmp12 ap_circulation.fmp12 ap_circulationarchive.fmp12 ap_MARC.fmp12 ap_photo.fmp12 ap_web.fmp12 ISBN collection utility.fmp12 📂 RC_Data_FMS 📂 ap_AthenaeumPro 📂 athpro_data 📂 alert 📂 barcodefont 📂 logo 📂 qr 📂 switch 📂 ap_catalog 📂 athpro_data 📂 background 📂 location 📂 media 📂 type 📂 ap_MARC 📂 athpro_data 📂 marc_image 📂 ap_photo 📂 athpro_data 📂 photo