1. Ori Miller, Aleph Support Manager
HTML Format s
Version 21 rep_ver #17640
Ori Miller, Aleph Support Manager

2. Agenda Introduction Configuration Example
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

3. Introduction Purpose of Enhancement
s from Aleph, up until v21, were in plain text, with an HTML file attached.
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

4. Introduction
The plain text display is not easily read, especially for tabular information, and therefor many libraries preferred to have the short message from …\Alephcom\tab\eng\MailHead.dat in the body of the
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

5. Introduction The difference between HTML and plain-text in Hebrew:
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

6. Introduction
Up until a few years ago, there were patrons who used a non HTML friendly reader. Nowadays, it seems like all patrons use modern Outlook / Gmail / Yahoo etc. and are accustomed to receiving rich text s.
Besides the fact that plain text wasn’t accepted by the patrons, it was also difficult for the system librarian to work on the letters formatting (XSL files), while checking if they look well in both HTML and plain-text formats.
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

7. Agenda Introduction Configuration Example
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

8. Configuration
New drop down option is available in the Mail Attachment attribute, HTML Body Only.
To activate it, add the following line to
<ADM Lib>/tab/pc_tab_exp_field.LNG and
<ILL Lib>/tab/pc_tab_exp_field.LNG:
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

9. Configuration For each patron we now have this new option:
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

10. Configuration Here is for ILL Partners:
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

11. Configuration And here is for ACQ Vendors:
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

12. Configuration TAB100: PLAIN-ONLY attribute included only two values:
"Y" and "N".
"Y" - Do not send an attachment. Only plain text in the body will be sent.
"N" - Send attachments depending on the Mail Attachment definition.
New value, "H", was added to the PLAIN-ONLY attribute. This new value provides the ability for not sending an attachment, Only HTML format in the body will be sent.
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

13. Configuration TAB100 header:
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

14. Configuration …\Alephcom\tab\Alephcom.ini
DefaultSendMethod= Possible values are
H (attached file), P(plain) or B(both).
Determines the default method (html, both, plain) when there no value comes
from server, such in cases when the was generated via the WEB OPAC.
Now we also have:
L (HTML Body)
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

15. Configuration
The library might want to change z303_plain_html to “L” for all Patrons (using PLIF), and then, upon specific requests change back to “B”.
Another option: Change to “L” for new students from now and on.
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

16. Agenda Introduction Configuration Example
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

17. Example We choose “L” for patron 00000036:
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

18. Example Send the “Patron Circulation Summary” by Email: And we get:
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach