Curator - Notes

• The website was developed using MS Expression Web 4 and Photoshop Elements 7. This being said some of the documentation is specific to these applications.
• MS Expression Web creates meta data to aid in the management of the website. If you are using MS Expression Web these folders and files do not need explanation. If you are using another desktop publishing application you will want to delete these folders and files. '_vti_*' and '_derived' should find them all.
• If you are using MS Expression Web 4 you will notice that there is a bug in the publish log. To get around this bug save the publish log. to your desktop and then open it in MS Word.
• Do NOT use the following characters in a listing: |

File Path

• File path may contain the following characters: lower case a-z, numbers 0-9, underscore '_', hyphen '-'.
• Linux and Unix do not like ampersand '&', use underscore or hyphen instead.
• Run Validate File Path to check for errors.
• HTML file names beginning with '00_' are local system files.
• HTML file names beginning with '99_' are local general test files.
• HTML file names beginning with 'ut_' are local utility files.

Padlock Categories

Avoid putting a listing in more than 1 web page. There are however a few good reasons to do so.
Run Find Duplicate Listings to see who the culprits are.

It is important to place the image and thumbnail files in their assigned folders, however it is not mandatory. Many locks can go in more than one category. To resolve the problem place the lock in the first category based on the rank. In the past we added a listing to all categories that it would fit in. Since implementing the Padlock Index it is no longer necessary. The structure of the *.htm file names is important. Before making changes check the service programs (*.hta).

Adding a padlock listing

• Copy an existing table row.
• Paste copied row.
• Change data in pasted row.
• It is important that you do not alter the structure of the listing. If you do, some of the service programs (*.hta) will not work. Before making any change check the service programs.
• Review Helpful Stuff for items you can copy and paste.

This is a fictitious listing

"10". 3" wide (Actual: 4.114" high x 3.032" wide). Stamped galvanized Steel body. Steel shackle. Post key. "W.BOHANNAN CO MARION OHIO U.S.A." is stamped on the obverse of the shackle. "PAT. APPL'D FOR" is stamped on the dust guard. The lock opens when turned in either direction. Catalog #: 10, first appears in catalog of 1930. (4.5). Mfg by: Wilson Bohannan Co. Augustus Van Kleeck Patent # 1855327. More... "The Scott Caley Collection"  This padlock requires further research

2802

Detail Pages

• Do not hyperlink to a detail page. Call ow_details(url [,watermark(y/n)]).
  When your detail page is a HTML file it must be named as: d_ (name) .htm. By doing this we have control over the detail pages.
  Do not write your own detail page, instead copy 00_d_details_shell.htm. This will allow us to make global changes if need be.
  You may turn off the watermark by not calling 'show_details_watermark();'.
• You may also call the following file types: jpg, bmp, png, gif, pdf.
  For example you may call ow_details('shared/stary_02.jpg') without watermark
  and ow_details('shared/stary_02.jpg', 'y') with watermark.
• When calling PDF files be aware that the local reader settings and browser type may render the page in different ways.
  'show_details_close()' and 'show_details_watermark()' are not used for PDF files as they would interfere with the PDF reader.

General Notes

• Record system maintenance in 'System Maintenance.log'.
• Backup is extremely important. Backup the website to an external hard drive on a daily basis and to a DVD on a monthly basis. Backup to a DVD even if you have not made any changes (DVD's can go bad). I use ImgBurn to backup to DVD's and have written a program to edit the file system.
• When viewing the website from your local 'c' drive the picture watermark is ignored. If you load the website to a drive other than 'c' you will have to change 'show_picture.htm' to reflect the change.
• Web pages that have a large amount of HTML tags that are created on the fly by JavaScript have a corresponding HTML base file. A good example of this is 'show_picture.htm' and 'show_picture_html.htm'. The HTML tag sections in 'show_picture_html.htm' are converted to JavaScript (by program) and subsequently dropped into 'show_picture.htm'.
• Microsoft is messing around with HTA's (HTML Applications). You may have to make changes in the future.
• The website has not been tested with the Edge browser as yet. This should be done to discover any incompatibilities.
• If you do not have a picture for a lock listing you must create a gallery image and thumbnail file to maintain the UIN integrity. 'No image' files reside in: root/graphics/no_image_01.jpg and no_image_01_tn.jpg. These files are already scaled and ready to copy.
• I added 'scroll_up_down.js' to this page to illustrate its use. I wrote this script to aide scrolling in long pages. A good example of use is hardware_co_list.htm.
• In a lock listing you may want to jump to 'Metropolitan Hardware Co' in 'hardware_co_list.htm'. To do this you would add this anchor '<a id="metropolitanhardware" />' in 'hardware_co_list.htm'. Now you can jump to it.
  We have hundreds of hardware company names that have not been added to the list. This is a big job and should be considered in the future.
• There are times that you will want to create another window on a specific domain such as Adobe. To do this you would first check 'ow_open_window.js' to see if it already exists if not add it. In this particular case you would add the following link: <a href="JavaScript: ow_adobe_reader()">Adobe</a>
• We are currently using jQuery v3.2.1 and it is named 'ap_jquery.js' in our library. You can read about it at jQuery.
  I added code in this page to disable the 'right mouse' context menu. You will notice that your 'right mouse' context menu is disabled. You can view the code directly after the <body> tag.
  Never call 'jquery-3.2.1.js or 'jquery-3.2.1.min.js' instead add the call to 'ap_jquery_user.js'.

Collector Community

• Root: ap_home/cc
• All files are created on the remote server. ap_home/cc and ap_home/cc_community.htm cannot exist on your local "c" drive.
• System Log: ap_home/cc/cc_sys_log.txt
• Application Lock: ap_home/cc/cc_app_lock.txt  (No Data - Creates A Single Thread)
• Last Date Community Page Created (Every 8 Hours if needed): ap_home/cc/cc_comm_file.txt
• User ID Files: ap_home/cc/id
• User Email Files: ap_home/cc/email
• User List Index Files Used To Create The Collector Community Page: ap_home/cc/ix
• System Files: ap_home/cc/system
• Register: ap_home/cc/system/"register_" plus User ID Key plus ".txt"
• Reset Password: ap_home/cc/system/"reset_" plus User ID Key plus ".txt"
• Backup Instructions...
• 1) Delete local ap_home/cc
• 2) Copy ap_home/cc from remote server to local ap_home/cc - USE DESKTOP PUBLISHING SOFTWARE, DO NOT USE FTP SOFTWARE.
• 3) Backup c:/00_ap_server to DVD
• 4) Delete local ap_home/cc