Shared SIs
MIT Open System Incidents
8192-44207
Opened when 3 of the 4 SOAP services were not working. Two are now working.
8192-56682
The vendor conversion page only lists Aleph 16 and 17. Requested the doc be changed to '127 and above'.
8192-57-73
Numerous corrections to the loader doc, too many to mention here.
8192-57903
DELETE function was not working in the Organization loader. This was fixed for awhile, but is broken again.
8192-58341
The log messages from the Org loader report on the status of IPranges, even though IPranges are not part of the Org record.
8192-61990
The KB update wizard was requesting the Oracel DBA password, then reflecting it to the screen in clear text.
8192-76325
Confusion about package SFX IDs, and Verde SFX IDs. Requested the following information be included in the User Guide.
The package SFX ID is drawn from the target service level in SFX. The Verde SFX ID corresponds to the SFX Internal ID as follows:
e-Interface SFX ID Interface Internal ID
e-Package SFX ID Target Service Internal ID
e-Constituent SFX ID Object Portfolio Internal ID
e-Standalone SFX ID Object Portfolio Internal ID
8192-77684
Localization instructions do not say that the SFX Default institute does NOT need a corresponding Library entry in Verde.
8192-91616
Numerous examples of confusing and inconsistent terminology in the documentation (compiled by Kim Maxwell)
In the Staff User's Guide (dated September 2007, hereafter referred to as the Guide) in Section 6.6.2 Acquisitions Loader, go to p.208 and look in the section called Defaults. Six mandatory fields are listed for which default values can be assigned. Let's follow three of those fields and see how they are named differently throughout this document and elsewhere.
(1) Acquisitions Licensor, as it is called on p.208, is called Default Vendor in the Task Properties window on p.209. If you look at p. 211 of the same Guide in Table 10. Acquisition Input File Fields, it is referred to a vendorCode. If you look at p. 235 of the Guide in B. Explanation of Fields, B.1. Acquisitions Fields, Table 12. Acquisition Fields, you'll see it referred to as VENDORCODE. And finally if you look in Verde itself, create an Acquisition Record on any e-Package and look at the Acquisition Tab; there you will see the field referred to as simply Vendor. Now you could argue that I should be able to intuit the subtle differences between vendorCode, VENDORCODE, and Vendor, but what am I to make of Acquisitions Licensor? In Verde terminology (and indeed in common language) "vendor" and "licensor" are truly not the same things.
(2) Renewal type / auto renewal. On p. 208 of the Guide, it says Renewal type. On p. 209 of the Guide, it says Default Auto Renewal (and gives the choices Yes, No, Ignore). On p. 211 it says autorenewal, and then indicates that the type of field is a number, and the field length is 1 character. On p. 233, it says AUTORENEWAL, and as a definition says "A clause which specifies whether renewal is automatic or explicit." Having read the last piece first, I was expecting this to be some sort of text field, based on the use of the word "clause." But it's not; it's simply a yes/no button.
(3) Here is something for which I can't seem to match up between Table 10 on p. 211-212, Table 12 on p. 233-235, and what I see in Verde itself. In Table 10 on p. 211, line 5 says orderDate. To what does that correspond? Is that what I see in Verde as the Start Date in the Acquisitions Tab of the Acquisitions Record? If so, I don't see anything that corresponds to Start Date in Table 12. There is something called ACQUISITIONSTATUSDATE, but I'm assuming that matches up with Acquisitions status date in Verde and #3 acquisitionStatusDate in Table 10.
These are just three examples I've found, just looking in Acquisitions. It would be really helpful if the naming conventions for fields were consistent throughout Ex Libris's documentation and could be easily matched up with what we see when we look at Verde itself. Table 10 gives you a number, a Field Name, a Type of Field, and a Field Length, while Table 12 gives you a code (that doesn't always match the Field Name in Table 10), a Data Element Name (which doesn't match anything in Table 10), and a Definition (which again isn't in Table 10). Frequently the Definition in Table 12 is simply a repetition of the Data Element Name, which really doesn't help define what the thing is (e.g., Number of Copies... what does that mean? Number of copies of what? and where is it in Verde itself?).
8192-91590
Incident Name: field length error in Acquisitions loader doc
On page 212 of the Staff Users Guide from Sept. 2007, field 26, pricingModel, is listed as TEXT 30. We were skeptical of that, because it's not clear what sort of note could be contained in 30 characters. Experimentation proves that it is not limited to 30 characters. We need to know the length of this field, and ask that you please fix the doc.
8192-95206
Sort order of Roles and Contacts on Org records changes randomly each time you visit or refresh the page.
8192-97140
Incident Name: 01MIT: Organization Records Enhancements Needed
1. Change Abbreviations for Organization Roles in Organization List
The list of Organizations includes columns for Organization Name, Code, and Roles. In the Roles column, some of the roles are abbreviated. Interface Provider is shortened to IP, and Licensing Agent is shortened to simply Agent. IP can also mean Internet Protocol, and Agent typically refers to a subscription agent. At first glance, it’s easy to misconstrue the meaning of both. Why abbreviate? Why not simply list the entire role name?
2. Expand Sort Options of the Organization List
The only sort option available is by name. The option to sort by Code should also be available. One should be able to click on the column heading Organization Name or Code and the list should sort for you. The first time you click, the sort is A-Z, the second time Z-A.
3. Expand Search Options
Jump To and simple scrolling are the only ways to find an Organization record. With just a few Organizations, this isn’t so bad. However, with hundreds of Organizations (which we anticipate we will have), this will become unwieldy very quickly. We should be able to search by keyword for anything in the Organization record (e.g., Name, Code, part of the street address, city, etc). At the very least, we should be able to search by Code, or at least Jump To code.
4. Add General Note Field
We need a Note field for Organizations beyond the Role Note field. If you would like to see examples of why we’d need such a note, please let me know. Field should be text with at least a 500 character limit.
5. Lengthen Display of Email Field
The Email field in the Organization Contacts is visually too short and can cut off an address with no clue (other than arrowing through the field) that there is more. As an example, take a look at the Customer Service contact in BLACKWELL in our Verde database.
6. Add Field for Account Number
There is no place to record our account number with the Organization. I've been sticking it in Contact Role Note, but that hardly seems appropriate. As an example, SPRINGER needs both our MetaPress ID and our Springer account number when we call with access issues. We need a place to record this information; field should be text (not all account “numbers” are actual numbers), with a 100 character limit. (No, the numbers themselves are never that long, but sometimes we have more than 1 account, or there is some explanation required that needs to go with the account number.)
7. Add Second and Third Lines for Address
Some addresses have more than one “street address” line. Verde only offers a single line, but should offer at least two lines and preferably three (as Aleph does). As an example, take a look at the Organization Contact record for Lesley Maw in the RSC record. I've crowded what should be three separate lines of street address into one. It's difficult to read all strung together like that and requiring arrowing through the whole field, and it's incorrect in terms of actual addressing.
8. Enlarge Display Box for Contact Role Note
Contact Role Note needs to display as a larger text box (not more characters necessarily, but more screen space). It's difficult to scroll and see more than a few words at a time. For an example, see the Organization Contact Record for Richard in the ACS record.
Kim Maxwell
8192-97871
The bug occurs when you attempt to update a constituent using the "Update - Activate" button on the package list. Our development team is aware of the bug and will release a fix in a future service pack.
Currently, there are two alternate ways to activate a journal in Verde:
a) Navigate to the eproduct screen. Set the e-Product Status to "production" and the Activation From date to today's date. Click Submit.
This option is most useful for activating a single title.
b) If there are multiple titles that you would like to update, you can use the Update - Approve button or the basket tool to give all relevant eproducts a selection status of "Approved." The package list should then be filtered according to Selection Status: Approved. The final step is to click the large Update button in the right-hand corner of the package list to give the selected constituents an eProduct Status of "production."
8192-101402
The December update seems to have broken the DELETE function of the Org loader.
8192-101819
More problems with the loader documentation.
8192-102774
The field that shows the date and user who last updated an Organization record is either not being set consistently or
is displaying inconsistently. Sometimes the correct data is displayed and sometimes not.
16384-4805
Invalid header template for the e-standalone loader.
16384-4790
e-standalone loader requires values in upper case that are specified in miced case in the User Guide.