...
SOLUTION: Check the native interface in question. If the same error message is received there, the issue lies with the native interface itself. If the native interface works properly, but the error continues in WebFeat, alert WebFeat support with the database name and the error message received. Include any action that you have done, such as attempting to replicate the issue in the native interface.
...
WebFeat contact information
Our two main webfeat WebFeat contacts are Kelli Smith and Rick Barr.
Contacting webfeat WebFeat by email:
Please e-mail Kelly and copy Rick on all technical support issues.
Kelli Smith: ksmith@webfeat.org
Rick Barr: rbarr@webfeat.org
Contacting webfeat WebFeat by telephone:
Feel free to contact webfeat WebFeat by telephone for emergencies. Here is a list of items that webfeat WebFeat considers to be emergencies:
- WF WebFeat is completely down
- Performance is really slow, there are issues with timing out, etc.
- User Authentication broken
- All databases for one vendor broken
- Library catalog broken - webfeat prioritizes catalogs over all other databases
Emergenices aren't necessarily limited to the above list, and determining what constitutes an emergency is basically up to us. Do not hesitate to contact webfeat WebFeat by telephone if you think the issue requires a quick resolution.