|
| 1 |
Keep your eye on the big picture
Optimizing access to library resources is the goal. Everything else is secondary. |
| 2 |
Establish an identity or brand
- Should the identity of the library match that of the parent organization? Does it?
- Create and carry through logos, color schemes and styles
- Gather these elements before you start to plan specific editing
|
| 3 |
Learn to be your own detective
Use the resources that are available to you:
|
| 4 |
Learn to analyze, deconstruct and interpret other libraries' WebPACs
Find examples of what you like and then figure out how it was done. If someone else has done it, it is possible. |
| 5 |
Adjust, don't reinvent
- Use the latest example set on CSDirect as a starting place
- Keep default file names
- Use the one directory
- Keeping with conventions will make for easier upkeep (not to mention with Help Desk troubleshooting)
|
| 6 |
Use shortcuts when you can
- Use tokens rather than coding where possible
- Use short forms over long forms
- Use default pages over customizable where possible
|
| 7 |
Pay attention to your data
- The WebPAC is an entry point and finding aid for the library's resources, but it can't be better than the underlying data
- Data will affect the WebPAC look-and-feel through:
- Scoping
- Limiting
- Indexing
- Searching in general
|
| 8 |
Keep the user in mind
- Remember, the ultimate goal in WebPAC editing is improving the end user experience
- Make it simple, friendly
- Your users (including Reference Staff) will thank you
|
| 9 |
Think about the relationship between the WebPAC and other, related products
- This includes ones you own now, or might own later
- It includes products from Innovative and from other vendors
|
| 10 |
Realize the WebPAC is an iterative process
It doesn't have to be perfect. A step in the right direction is a good thing. Iterate & improve. |
