Showing posts with label Voyager. Show all posts
Showing posts with label Voyager. Show all posts

Friday, February 18, 2011

The Status of the Withdrawn Status

We’ve had some problems recently with patrons being sent to other campuses to get items that turned out to be withdrawn, so I wanted to take a second to go over that status and how it currently displays.

When items are withdrawn from the collection, they are given the item status of “Withdrawn”, which allows me to run a report and pull them out for Sonya, who removes/suppresses the records in the catalog and takes our holdings off of the WorldCat record, if necessary.

Now, unfortunately, this item status doesn’t display in GIL Classic. That’s why people withdrawing items have to add the temporary location of “WITHDRAWN,” in addition to the item status. This temporary location does display in GIL Classic. We’ve put it in all caps to make it as noticeable as possible, and it's pretty large, but that’s the best we can do given the limitations of the software.



Now, GIL-Find is a little more flexible about statuses than GIL Classic, and I’ve been working with the server site to get statuses to display in a more meaningful way. When the new code rolls out soon, we may even start seeing “Withdrawn” in GIL-Find. Here’s a screenshot from the testing code.



Whether they’re using GIL-Find or GIL Classic, please look for this temporary location and/or status in the holdings record before telling someone an item is available and remind your part-time staff to do so. Patrons have gotten understandably upset after driving to another campus for a book that wasn’t there.

Thanks everyone! Please let me know if you have any questions.

Wednesday, September 23, 2009

Yep. Another OPAC Bug.

This is rapidly becoming the Bug Blog, isn't it? (Say that five times fast. Bug Blog. Bug Blog. Blug Blog. D'oh!)

Anyway, just wanted to let you all know that I've confirmed that the odd OPAC behavior that some of you have been reporting is, in fact, a known bug.

After doing a Quick Search in the OPAC, you can sort your results by Title, Author, or Pub Date. However, if you use one of these sorts, you will be taken to the Exact Search screen when you click on a hit, not to the full record for your hit.

This shouldn’t happen when you're using the Exact or Keyword Searches. If you do a Keyword Search and use the index "Keyword Anywhere", this should give you the same results you'd get with the Quick Search, only you'll be able to sort them.

Of course, saying that this a known bug doesn’t mean that I, or the server site, can fix it, sadly. But, it's nice to know it's known, right? :)

It may be something that is fixed in later versions of the OPAC software, but last I heard we were not upgrading WebVoyage (the software behind the OPAC), since we're moving to GIL-Find. GIL-Find, knock on wood, should not have these sorting problems.

Please let me know if you have any questions.

Friday, August 28, 2009

OPAC Call Slip Bug w/ Newton Faculty DVDs

Eagle Eye Amy B. alerted me to a problem one of her patrons had in requesting something in the OPAC, and, as a result, I've uncovered an odd bug that everyone should be aware of.

If a patron is trying to request a DVD for intercampus loan, through the OPAC, and there is a Newton Faculty DVD holding on the record, there is a small chance that the request will be denied and they'll get that "Your Patron Initiated Request failed" message.

As best as I can tell, here's what's happening. The Newton Faculty DVD location is not available for intercampus loan. (It's Call Slip that's running this.) If Call Slip latches onto the Newton Faculty DVD holding first, instead of seeing that it's unavailable and just rolling over to the next available holding, it's just denying the request.

So, if you encounter a patron having this problem, go into Circulation and place the request for them on the exact item record that they want. That will work just fine. Then, drop me a line with the title you're having problems with and the barcode of the item you placed the request on. I won't bore you with the details, but I believe that part of this problem is caused by the MFHD ID numbers, and I may be apply a little manual fix to make sure that it doesn't happen in the future on that bib record.

I'm going to report this to Ex Libris, but there's no telling when or if they'll fix it. So, just be on the lookout for it and tell me whenever you find an instance of this behavior. Just let me know if you have any questions!

Tuesday, February 03, 2009

Clarkston Water Leak

As you may have already heard, Clarkston has been visited by its now annual water leak. This time it got the circulating stacks, call numbers N through P.

Books that were in that area and not water damaged have been temporarily relocated to trucks on the right side of the aisle. Books that have been too damaged to circulate have been given the location "Clarkston Water Damaged" in the OPAC, which should prevent patrons from requesting them. Eventually, these records will be removed from the OPAC, but we need to leave them in there for the time being to run reports on the damage.

Note: This location will prevent students from requesting these items in the OPAC, but I have no way of preventing librarians and staff from requesting them in the Circulation Module, so please double check the location of any Clarkston book before putting a request on it in the back-end. If the location is Clarkston Water Damaged, please inform the patron that these books have been permanently damaged by a water leak and removed from circulation.

And please let me know if you have any trouble with the OPAC or the back-end not behaving as expected with these items.

Thanks, everyone!

Monday, November 17, 2008

Holds, Recalls, and Call Slips. Oh My!

Hi all. There's been a little confusion of late, about the ins and outs of holds, call slips, and recalls. It is all pretty unintuitive, so I've done my best to break it down here.

Hold = This can only be done by a librarian or certain staff members, through the Circulation module. A hold only works its magic when an item is discharged. That's when that "Item on Hold" slip prints out. So, you should never ever ever place a hold on an item that is not charged. That hold will never announce itself and will expire as the item languishes on the shelf. If an item is checked out, however, and another patron wants it, the hold is the way to go. Pay attention to which kind of hold you place, a title hold (for all items on the title) or a copy hold (for one particular item). Keep in mind a title hold essentially puts a hold on every item, and the OPAC display will reflect such. Also, please make careful note of the expiration date of the hold. It defaults to 10 days after the date the hold is placed, which really isn't very long. The hold could easily expire before the item is discharged, so I'd recommend setting that date at least a month out. [Update: If an item is In Process, a hold can be placed on it, by a librarian or staff member, in the Circulation module. Patrons cannot place holds on In Process items in the OPAC. Never place a call slip or a recall on an In Process item, only a hold.]

Recall = Again, only available to librarians in the Circulation module. This is kind of similar to a hold, except that a recall notice probably prints out for the patron who currently has the material charged, and they may start to accrue fines if they don't return the item by the recall date. (I'd have to really scrutinize the circ matrix to see if that's actually the case.) You can also place a title or copy recall. I don't think that we're really using recall too often, which is probably for the best. I'm not sure how well it really works, and I think the general consensus is that the patron who originally charged the item should have their fair time with it. [Update: Recalls are not currently enabled in Voyager and the Circulation Committee has chosen not to enable them at this time.]

Call slip = Call slip is available to librarians, and some staff members, in the Circulation module, but also to patrons in GIL@GPC. When a patron places a request for something in the OPAC, they're automatically using call slip. Whether from the Circulation module or from the OPAC, you can only call slip items that have a status of "Not Charged." If you try to call slip something that is charged, you'll get an error message. Call slips are automatically copy level actions, you cannot place a call slip for every item on a title. So, call slip should be used for moving specific, and uncharged, items from one campus to another.

A little caveat, don't try to put both a hold and a call slip on the same item/title. If the item is charged, you'll get an error message when you do the call slip, and if the item isn't charged, the hold will cause call slip to lock up, resulting in a cryptic error message. (Whenever you have a call slip that won't fill, it's probably got a hold on it too. Just make sure that the hold and call slip are for the same person, then cancel the hold.)

Nutshell version: If it's charged or has an In Process status, do a hold. If it's not charged, do a call slip. Never, ever do both. In the back end, you may place a hold or a call slip, but patrons requesting something in the OPAC are always doing a call slip.

Let me know if you have any questions.

Update: Mary Ann has graciously shared the handout she's created for Dunwoody's circ and reference desks, if anyone would like to use it. It's a great quick reference.

Friday, November 14, 2008

By Popular Demand: OPAC Tweaks!

As you may or may not know, with the way the server sites are set up, I don't have a lot of direct control over GIL@GPC and one of the things I have no access to is the general design and layout. However, that doesn't mean that you shouldn't send me suggestions. I do have a man on the inside, who, while very busy, has been gracious enough to make some changes for me that I think you'll all be very happy with.

1.) On the Exact Search page, we now have a little extra clarification for the title and author searches, about last name first name and dropping initial articles. I notice that it's all in bold though, and I'm wondering if it would read better if only the index name (i.e. "Title," "Journal Title," etc.) were in bold. Let me know what you think.

2.) When you have a failed search and get the "No matches were found in this catalog" message, we've now got a note about dropping initial articles and the bullet point about asking a librarian for help is actually hyperlinked to the Ask a Librarian page.

Of course, we'll be getting a brand new OPAC with our Voyager 7 upgrade, which I have every reason to believe is coming up in December, but I'll try to make sure that these tweaks carry over.

Wednesday, July 23, 2008

That Which We Call NonPrint, By Any Other Name ...

As you all may know, the NonPrint department is now a part of the Clarkston library, rather than a unit of Technical Services. I’ve just edited all of the locations to reflect this. So, NonPrint Popular DVD is now Clarkston Popular DVD, and so forth. You may still see NonPrint On Order here and there, I can’t change that to Clarkston On Order since that location already exists, but, as we finish up the NonPrint backlog, those will shake out.

Now, these changes merely affect the way these locations display in the OPAC and the staff side of Voyager. The location codes cannot be edited and will remain NPPopDVD, and so forth. I’m fairly certain that the catalogers are the only people using the location codes, but, just in case, I wanted to mention that they’re staying the same.

NonPrint still needs to keep their happening location, NONPRINT CIRC DESK, and their own Callslip queue. But, outside of that, everything that once said “NonPrint” should now say “Clarkston.” If you don’t see these changes in the staff side of Voyager, just close the client and restart it.

Please let me know if I missed anything. Thanks!

Thursday, June 05, 2008

Error Reporting Comes To the OPAC!

Just wanted to let you all know that I've asked the server site to set up an error reporting form in the OPAC and it's now up and running. Just click on the image below for a full screen shot.



Right now, technical restrictions only allow this form to be emailed an internal address, i.e. Jim @ the server site, but he'll forward anything he receives to me and I'll take care of it.

Give it a try and let me know what you think!

Update: To clarify, this form is to be used for correctable errors, like the wrong class number, no holdings on a bib, "No Information Available" on an item record, something misspelled, etc. Continue to report OPAC bugs directly to me with a complete description (including the date and time you encountered the bug and what you were doing right before), and copy and paste the URL from the page giving you the error.

Thursday, February 07, 2008

Odd Block Behavior in Voyager

I've learned a couple of things about the way blocks behave in Voyager, and I wanted to share with everyone.

1.) Occasionally, in a patron's web account, you may see that they are blocked, but it doesn't say why. Under the "Patron Blocks" section, it will say "Block Reason," then fail to elaborate. If you come across this, please let me know. (I'll need the patron's name and 900#.) This is a bug, and our server site can often fix it, making the block reason appear.

2.) Patrons will be blocked in their web accounts simply for reaching their charge limit in a particular item type. This is the only way that limits can work in Voyager. Sad, but true. For example, if a student has 3 DVDs charged out (the limit for the GPC STUDENT patron group), they will be blocked in their web account and will be unable to renew any charged items online, regardless of item type. However, they can still request items in the catalog, charge other item types, and staff with Circulation Supervisor privileges in Voyager can renew items for them in the Circulation module. (Unfortunately, I think the system would let them request another DVD, but it won't let them check it out until they return one of the 3 they have charged.)

If anyone has any questions about this, please just let me know.

Friday, January 04, 2008

Voyager Upgrade '08

Just wanted to let you know that I've just received confirmation of our Voyager upgrade schedule. The server will be upgraded during the evening of Sunday, Jan. 6, 2008. Which means that, when you come in on the morning of Monday, Jan 7, 2008, the Voyager clients will be down. I'll be working with OIT to remotely push out the upgrade, like I have in the past, and I'm striving for the minimum down-time possible, but just to be on the safe side, please be prepared to be down for the first few hours of the day.

Please remember to leave your PCs on over the weekend, this is crucial if you won't be in on Monday morning. You can log out of your profile (Usually, Start > Log Off > Log Off on XP machines) but the computer MUST BE POWERED ON when I start the upgrades on Monday morning. If it isn't, then I have to get the liaison to power it on, which may involve tracking down office keys, and it always makes for an aggravating morning for everyone involved.

I'd like to issue a hearty thanks to the upgrade liaisons for providing their assistance. They will be visiting you all on Monday morning, letting you know when I'm about to start your campus's upgrade, at which time you'll need to stay off of your computers. When the upgrade is over, they'll let you know and check to see that Voyager was successfully upgraded on your machine. Please report any problems with the upgrade to your liaison as soon as possible.

Clarkston: Amy Yang
Decatur: Adrienne Graham
Dunwoody: Pete Bursi
Newton: Rebecca Rose
Technical Services, Media Services, and NonPrint: Tessa Minchew

If you have any questions about this process, please just let me know.

Monday, August 06, 2007

IMPORTANT: Change to Voyager Upgrade Date

To accommodate the schedule of my gracious OIT contact, I have to upgrade the Voyager clients beginning around 2:00pm on Tuesday, August 7. Since the server is being upgraded that evening, Voyager will be inaccessible after I do our upgrade. Circulation & Media Services should be prepared to do manual check outs from 2:00pm until closing, and anyone else who has any work to do in Voyager should try to do it before 2:00pm. If you are leaving the office before 2:00pm, please leave your computer on, just log off of your profile.

When you come in on the morning of August 8, our server will have been upgraded and the clients should work just fine. Your upgrade liaisons will be giving you a heads-up before the upgrade begins.

Clarkston: Amy Yang
Decatur: Adrienne Graham
Dunwoody: Carmel Chaille
Newton: Rebecca Rose
Tech Serv, Media Serv, NonPrint: Tessa Minchew

Please let me know if you have any questions, and thanks in advance for your patience during the upgrade.

Wednesday, July 25, 2007

Voyager Upgrade Date Set

Hi everyone. Just wanted to let you know the date of the Voyager upgrade has been set. Our server will be upgraded on the evening of Tuesday, August 7. This means I will be upgrading Voyager clients on the morning of Wednesday, August 8. This process will work much as it has the last few times. I will be performing the upgrades remotely, and each campus will have an upgrade liaison to facilitate the process and report problems to me. Here are the folks who have graciously agreed to be your upgrade liaisons.

Clarkston: Amy Yang
Decatur: Adrienne Graham
Dunwoody: Carmel Chaille
Newton: Rebecca Rose

I'll be handling the liaison duties for Technical Services, Media Services, and NonPrint.

Remember, when the server is upgraded, the Voyager clients will not work until they are also upgraded to the new version. So, Circulation, especially, should be braced for a little downtime, but I will do my best to turn the upgrades over as quickly as possible, and, on that note, there are a couple of things that you can all do to help me achieve that goal.

1.) This week, your liaison will be checking the IP address of every computer requiring a Voyager client, and reporting that information to me. If you need the client, make sure you make it on this list.

2.) Please remember to leave your PCs on on Tuesday evening, this is especially important if you won't be in on Wednesday morning. You can log out of your profile (Start > Log Off > Log Off on XP machines) but the PC must be POWERED ON when I start the upgrades on Wednesday morning. If it isn't, then I have to get your liaison to power it on, which may involve getting office keys, and always fouls up my workflow.

If anyone has any questions about the upgrade, please just let me know. And thanks in advance for your patience!

Wednesday, July 18, 2007

Another Voyager Upgrade On Its Way

Hi everyone. I just learned that we will be upgrading from Voyager 6.2.1 to Voyager 6.5.1, somewhere between Friday, August 3 through Friday, August 10. I won't know the specific date until I hear from our Service Site Coordinator, but I wanted to give you all a heads up.

Most everyone knows the drill by now. The server will be upgraded, usually in the evening, and after this you will be unable to access Voyager from your PCs until I have upgraded the clients. This has to happen on each and every PC that runs Voyager. The last couple of times, OIT has been gracious enough to help me push out a script to each computer, which dramatically reduces our downtime. Otherwise, I would have to drive to each campus, and upgrade each PC by hand, which can take quite a while.

I've also found it helpful to have an "upgrade liaison" on each campus, to check that the script has run correctly on everyone's PC, relay questions, etc. I'm going to be contacting folks about doing that and I'll let you know when we have our victims, *ahem*, I mean lucky volunteers.

For a little more info about 6.5.1, allow me to quote the esteemed Phil Williams. "One of the primary features of this upgrade will be the implementation of the "UB Local Block Policies". The Service Site Staffs will set the appropriate UB Local Block Policy Definitions in accordance with established GIL Express standards. We are anticipating that GIL Express transactions will continue through the upgrade period, however if difficulties do arise a notice will be sent to the listserv and a message will be put on the GIL Universal Catalog web site."

I would advise that everyone read the release notes for this version.

http://download.gil.usg.edu/gold/0605/relnotes.pdf

If, after that, you're feeling especially curious, please feel free to peruse the rest of the 6.5.1 documentation.

http://download.gil.usg.edu/gold/0605.html

Both of these links will ask you for our GIL Knowledge Base username and password (which is the same as the Endeavor Knowledge Base username and password). Give me a call if you've forgotten it.

If anyone has any questions, please drop me a line. And thanks in advance for your patience during the upgrade!

Monday, June 04, 2007

Rockdale/Newton Becomes Newton

Just wanted to let everyone know that, with their move, the Rockdale campus will now be known as Newton. To that end, I've changed all the instances of "Rockdale" to "Newton" in the Voyager back-end, the OPAC, and on the webpages I have control of. The other webmasters will be changing their pages shortly, if they haven't already.

For those who use the Cataloging module, you will notice that drop-down menus are reading something like "Newton Book," but the location code will still be "ROBook." I'm afraid that Voyager doesn't allow for changing permanent location codes, just the way they display, so we're stuck with this. Those using Acquisitions and Circulation probably won't notice this. I think all you ever see is the display name, which will be "Newton Book," "Newton Reference," etc.

If you have any questions, please let me know.

Update: In the OPAC, the Location field of the Narrow My Search limits and in the Quick Limits under the Exact Search still say "Rockdale." Bob Trotter will have to change that and I emailed him on 4/1.

Wednesday, February 21, 2007

Upgrade to Voyager 6.2

Just wanted to let everyone know that the server site has informed us that we must undergo another Voyager upgrade next week. Apparently v.6.2 has some needed fixes (see attachment). It has been road tested by the folks at UGA, and passed their approval, so everything should be fine. (I have some hopes that it will help with our OPAC-issues, but there are absolutely no guarantees on that, so keep sending in those problem reports until you hear from me otherwise.)

As of now, the schedule I've been given for the upgrading GPC's server is the evening of Monday, February 26th. This means that when you come in on the morning of the 27th, Voyager will be down on everyone's PC. I am working with OIT to prepare another packet delivery system and we have high hopes that it will work as smoothly as it did last time. If it does, down time will be minimal. If not, I may have to drive to your campuses to upgrade PCs manually. Let's all keep our fingers crossed that it doesn't come to that. I don't want you to experience any more down time than is absolutely necessary.

As I understand it, GIL Express transactions are expected to function normally between 6.1 and 6.2 libraries, so no GIL Express downtime is expected. Please report any problems you might experience.

Thanks in advance for your patience! Hopefully this will be our last upgrade in 2007.

Thursday, February 01, 2007

Hello, and wildcard searching

First of all, hello! I am Amy Eklund, one of the new catalogers in Tech Services. I am really glad to be here at GPC and I am really enjoying working here (I started Dec. 1). I look forward to meeting those of you I haven't had the chance to meet yet.

Secondly, I wanted to mention something I noticed while doing a recent database maintenance project. I have been using truncation and wildcard searching in the Voyager cataloging module (which I didn't know was possible until I began working here) and that got me wondering about those capabilities in GIL, as well. So, after some playing around in GIL and reading all the "Help" documentation (particularly the sections on "Searching" and the "Technical Documentation"), I discovered that both right-truncation (using ?) and wildcard searching (using % anywhere in the word) are possible in keyword search and command search in GIL. Truncation is mentioned in the "Help" documentation, but wildcard searching is not. I can see how wildcard searching might be very useful if you haven't been aware of it before, for instance if a patron comes in asking for a book about Powerpoint by "Munson" but they are not sure whether it is spelled "Mansen", "Munson", "Monsen", or "Munsen" (so you could do a fielded keyword search for "M%ns%n" with a keyword search for Powerpoint).

Hope this is useful for you if you didn't already know about it, and happy searching!
Amy

Thursday, December 07, 2006

Voyager Upgrade Looming

[I sent a message about this to everyone's director, to forward along, but I thought that I'd post it here too, just in case anyone missed it.]

The slot GPC has been allotted for the Voyager upgrade is Wednesday, December 20th, beginning that evening and hopefully ending by the following morning or afternoon.

I'm exploring the possibility of a remote upgrade with OIT, which is very gracious of them. However, if we can't get that working, I'll be manually upgrading every PC running Voyager, just like John did last year, starting December 21st. I will make it my only priority, but even devoting all of my time to it, it may take a while for me to get to every campus, so your patience will be greatly appreciated.

Circulation (for GPC materials) will be down until the machine you run it on is upgraded. GIL Express will be down for the duration of the entire upgrade. This means that all USG institutions must be successfully upgraded before GIL Express service can resume anywhere. The estimate is that GE will be down from December 13, 2006 through January 5, 2007. This service suspension has been discussed at length on the UC/UB listerv, and I imagine that GPC circulation staff are familiar this discussion.

That's about all that I know right now, but if you have any questions, please just drop me a line. I'll keep you posted as more details become available.

Monday, November 06, 2006

USG Upgrade to Voyager 6.1

No specific dates for GPC yet, but they're predicting sometime this December and I expect that I'll start working on our individual machines shortly after that. (I have to touch each PC that has the Voyager client.) The Voyager 6.1 documentation has been placed on the GIL Download web site. Remember that access to the GIL Download web site requires our SupportWeb user id and password. If you've forgotten it, drop me an email and I'll send it to you.

The GIL Download site has user guides for each module in Voyager 6.1, but they're extremely long (828 pages for circulation alone). I would, however, recommend taking the time to read the release notes, which are a much more manageable length (9 pages). Some of the highlights are search enhancements in WebVoyage and the Voyager staff interface, improvements to the display and sorting of results lists in the staff interface and the display of results lists in WebVoyage, and ISBN-13 support.

This is the gist of what I know right now, but please feel free to send me your questions and I'll do what I can to get them answered.