| Warning Due to server maintainance, the jOPAC widget will be down for the next few weeks. We hope to bring back this service in a refreshed version soon and will keep you informed. |
Current Version: 0.9
Status: Beta
What is it about?
The jOPAC is an integrated OPAC widget. It eases searching the library catalogue by integrating it into various platforms, and it introduces some nice extras. A list of all platforms with installation links can be found below.
If you don't use any of these platforms yet, we recommend iGoogle since it has received most development efforts so far. For this, simply click on this link to add the jOPAC widget to your personalized google page.
Feedback
For bug reports or comments on jOPAC, please use the jOPAC feedback site.
Installation
For installation, click on the following links according to your chosen platform, and follow the standard installation:
For Google Desktop, simply copy and paste this url into the top-right gadget search field: http://dev.public.jacobs-university.de/live/iGoogle.xml. We recommend using the Widget docked-off the sidebar, allowing easy&fast double-shift access to the OPAC!
Demo
Two platform - independent demos can be found below. You can include this widget in any Web Page as long as you got <inline> or <script>-writing permission. For a live demo, test the inbuilt widgets below. The left is realised with the a BlogWidget Javascript - allowing you to set some preferences, the right is realised with an inline frame.
To make the left work, simply add the following to your web page:
<script type="text/javascript" src="http://www.netvibes.com/js/UWA/load.js.php?env=BlogWidget"></script> <div id="UWAjOPACWidget" style="height:600px">Loading the jOPAC Widget</div> <script type="text/javascript"> var BW = new UWA.BlogWidget( { container: document.getElementById('UWAjOPACWidget'), moduleUrl: 'http://dev.public.jacobs-university.de/live/jOPAC.html' } ); BW.setConfiguration( { 'title':'jOPAC', 'height':'500', 'borderWidth':'1', 'color':'#aaaaaa', 'displayTitle':true, 'displayFooter':true }); BW.setPreferencesValues( { 'limit':'10', 'display':'compact', 'language':'auto' } ); </script>
or for the right inline frame:
<iframe src="http://nvmodules.netvibes.com/api/uwa/frame/uwa_standalone.php?moduleUrl= http://dev.public.jacobs-university.de/live/jOPAC.html frameborder="0" height="500" scrolling="AUTO" width="500" frameborder="0"></iframe>
Source code
The source code for jOPAC can be found here. If you happen to work on jOPAC, I would appreciate a short notice - so I can guide you through the installation and coordinate further development.
External Libraries
More information on this settings file will be provided soon. Alternatively you can also download the Source Code and run your own jOPAC instance.
Acknowledgement
Many thanks to Skaldrom Y. Sarg for his nice tutorial on uwa widgets.
Special thanks to Mark Jordan - without his yaz-based php-OPAC the data model would have been severely more complicated.
http://www.netvibes.com/js/UWA/load.js.php?env=BlogWidget is currently not available. You should better host it at your own server! Having to rely on Netvibes is not a good solution, if it's not really needed.
I just installed the MAC dashboard widget – wow, very nice. (I tried modifying some settings once and when I clicked 'done', it vanished all my dashboard widgets at the same time.) I've also added it to netvibes and it looks great using the one column view with my theme.
When I set to "compact" view, I get the different tabs (holdings; map, etc.); however, when I set to 'extended' view, I only get hit lists and none of the links work. This behavior is the same in the MAC dashboard widget and netvibes. ??
Mia
I'm glad you like what works so far and appreciate your bug report. I forgot some variables when I made the code look nicer - thanks for pointing me to it. I'm not sure why the dashboard settings caused you troubles on the other dashboards - but will have a look inside this soon.
If you find any other problems or you got some other good suggestions, please tell me.
This is so cool! Now, one can search books in the IRC from my iGoogle page! It even has a map of the stacks showing the exact shelf where the book is physically located! Very impressive, indeed!
Thanks a lot
I was wondering, if you find the shelf precisely enough for a book location, or whether more detailed information (e.g. the board within the shelf) would be a lot more helpful?
Indeed, info about the exact board on the shelf would be helpful ... But this is already nice !! One suggestion : when a book is not available, I think it would be better to display the message in the holdings tab, or even in the search results list. This way, when I search for a book, I know for sure that it's not there from the start. Good job !
Hello,
how can I prevent the widget from setting the focus on the text input element after loading?
The javascript sets the focus, except if the context is igoogle.
But if the widget is embedded in any other page, the focus is set. In our case it is inserted into a longer page, after loading the browser jumps down in order to show the focused element, but we would like to not have this behaviour.
Best regards,
Christian Kirchhoff
Hi Christian,
I need some more information on how you use the widget before I can answer this:
a) Do you host the widget yourself, or do you use our installation?
b) Do you use the BlogWidget or iframe - embedding?
c) Do you want this to work on one or multiple domains? If one, which?
Thanks,
John
Hi John,
thank you for your kind offer to help.
Here is the page where we included the search widget: http://www.editura.de/new/web20.html
a) your installation
b) we use the iframe
c) one domain
What I tried was: I made a local copy of the html code of http://dev.public.jacobs-university.de/live/jOPAC.html
Then, in the jOPAC.onLoad function, I commented out the lines:
// Do not steal the Igoogle focus
/*if (!widget.environment.google)
widget.elements['inputs']['what'].focus();*/
and referenced that html file in the iframe. I refreshed the page and it didn't jump down to the text input element any more. But the search didn't work any more, because I didn't link via http://nvmodules.netvibes.com any more.
As for me, I would just need the page without that line of code that sets the focus after load.
Thanks,
Christian
I added your domain to be ignored by the focussing. Thanks for spreading the word on the widget for us. ![]()
Wow, that was fast!
Thank you so much, John.
Best regards,
Christian

Neither Demo nor Mac Widget works. Is there a special way to configure it?