rebuild_nozebra.pl error

classic Classic list List threaded Threaded
18 messages Options
Reply | Threaded
Open this post in threaded view
|

rebuild_nozebra.pl error

Ming214
Hi all,

I got an error when I tried to add new biblio to koha.

Error:Can't call method "as_usmarc" on an undefined value at /usr/share/koha/lib/C4/Search.pm line 2133

I tried to rebuild the index with
perl /usr/share/koha/bin/migration_tools/rebuild_nozebra.pl

It runs very slowly and I got errors like
1417 problem with :1900 : Cannot decode string with wide characters at /usr/lib/perl/5.8/Encode.pm line 186.
<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/ standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>02798cam a2200685 a 4500</leader>
  <controlfield tag="001">000040660987</controlfield>
  <controlfield tag="003">AuCNLKIN</controlfield>
  <controlfield tag="005">20070330205916.0</controlfield>
  <controlfield tag="008">060824s2006    xnaa     b   s000 0 eng d</controlfield>
  <datafield tag="020" ind1=" " ind2=" ">
    <subfield code="a">0734728743 (print)</subfield>
  </datafield>
  <datafield tag="020" ind1=" " ind2=" ">
    <subfield code="a">0734728751 (online)</subfield>
  </datafield>
  <datafield tag="040" ind1=" " ind2=" ">
    <subfield code="a">NSL</subfield>
    <subfield code="c">NSL</subfield>
    <subfield code="d">ANL</subfield>
  </datafield>
  <datafield tag="042" ind1=" " ind2=" ">
    <subfield code="a">anuc</subfield>
  </datafield>
  <datafield tag="043" ind1=" " ind2=" ">
    <subfield code="a">u-at-ne</subfield>
  </datafield>
  <datafield tag="050" ind1=" " ind2="4">
    <subfield code="a">DU 0125</subfield>
  </datafield>
  <datafield tag="082" ind1="0" ind2="4">
    <subfield code="a">362.76809915</subfield>
    <subfield code="2">22</subfield>
  </datafield>
  <datafield tag="099" ind1="5" ind2=" ">
    <subfield code="a">40960212</subfield>
  </datafield>
  <datafield tag="245" ind1="0" ind2="0">
    <subfield code="a">Breaking the silence :</subfield>
    <subfield code="b">creating the future : addressing child sexual assault in Aboriginal communities in NSW /</subfield>
    <subfield code="c">Aboriginal Child Sexual Assault Taskforce.</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a">Wolli Creek, N.S.W. :</subfield>
    <subfield code="b">ecoDesign ecoPrint,</subfield>
    <subfield code="c">c2006.</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">viii, 335 p. :</subfield>
    <subfield code="b">ill. ;</subfield>
    <subfield code="c">25 cm. +</subfield>
    <subfield code="e">1 CD-ROM (4 3/4 in.)</subfield>
  </datafield>
  <datafield tag="500" ind1=" " ind2=" ">
    <subfield code="a">Cover title.</subfield>
  </datafield>
  <datafield tag="500" ind1=" " ind2=" ">
    <subfield code="a">"NSW Aboriginal Child Sexual Assault Taskforce members: Ms Marcia Ella-Duncan."--Prelim. p.</subfield>
  </datafield>
.....................

I guess the index is broken but when I run this script to rebuild the index, it throws errors.
Anyone knows what happens? Thanks in advance.

Ming214
Reply | Threaded
Open this post in threaded view
|

Z39.50

Lino Tremblay
Hello List,

I'm trying to set up my Z39.50 targets, and I'm sometimes getting this error message:

Koha error

The following fatal error has occurred:

utf8 "\xE2" does not map to Unicode at /usr/lib/perl/5.8/Encode.pm line 166.
Apache Server version: Apache/2.2.3 Server built: Jan 27 2008 18:09:58
Koha 3.00.00.107
Koha DB 3.0000107
MySQL mysql Ver 14.12 Distrib 5.0.32, for pc-linux-gnu (i486) using readline 5.2
OS Linux koha3 2.6.18-6-686 #1 SMP Fri Jun 6 22:22:11 UTC 2008 i686 GNU/Linux
Perl 5.008008


Anybody knows where it's coming from?

Thanks!

Lino

_______________________________________________
Koha mailing list
[hidden email]
http://lists.katipo.co.nz/mailman/listinfo/koha
Reply | Threaded
Open this post in threaded view
|

Re: Z39.50

Jesse Weaver-2


On Tue, Dec 9, 2008 at 7:16 AM, Lino Tremblay <[hidden email]> wrote:
Hello List,

I'm trying to set up my Z39.50 targets, and I'm sometimes getting this error message:

Koha error

The following fatal error has occurred:

utf8 "\xE2" does not map to Unicode at /usr/lib/perl/5.8/Encode.pm line 166.
Apache Server version: Apache/2.2.3 Server built: Jan 27 2008 18:09:58
Koha 3.00.00.107
Koha DB 3.0000107
MySQL mysql Ver 14.12 Distrib 5.0.32, for pc-linux-gnu (i486) using readline 5.2
OS Linux koha3 2.6.18-6-686 #1 SMP Fri Jun 6 22:22:11 UTC 2008 i686 GNU/Linux
Perl 5.008008


Anybody knows where it's coming from?

Thanks!

Lino

_______________________________________________
Koha mailing list
[hidden email]
http://lists.katipo.co.nz/mailman/listinfo/koha


Is this on the z39.50 target administration page? If so, are there any accented or otherwise not-english characters in the name of the server or any other part of the target?

--
Jesse Weaver
Software Developer, LibLime

_______________________________________________
Koha mailing list
[hidden email]
http://lists.katipo.co.nz/mailman/listinfo/koha
Reply | Threaded
Open this post in threaded view
|

Re: Z39.50

Joe Atzberger
Specifically, there is apparently one with an "â" character.  I'm not sure why this is causing a crash at this point, but apparently it does. 
--Joe

On Tue, Dec 9, 2008 at 1:33 PM, Jesse Weaver <[hidden email]> wrote:
On Tue, Dec 9, 2008 at 7:16 AM, Lino Tremblay <[hidden email]> wrote:
Hello List,

I'm trying to set up my Z39.50 targets, and I'm sometimes getting this error message:

Koha error

The following fatal error has occurred:

utf8 "\xE2" does not map to Unicode at /usr/lib/perl/5.8/Encode.pm line 166.
Apache Server version: Apache/2.2.3 Server built: Jan 27 2008 18:09:58
Koha 3.00.00.107
Koha DB 3.0000107
MySQL mysql Ver 14.12 Distrib 5.0.32, for pc-linux-gnu (i486) using readline 5.2
OS Linux koha3 2.6.18-6-686 #1 SMP Fri Jun 6 22:22:11 UTC 2008 i686 GNU/Linux
Perl 5.008008

Anybody knows where it's coming from?

Thanks!

Lino

Is this on the z39.50 target administration page? If so, are there any accented or otherwise not-english characters in the name of the server or any other part of the target?

--
Jesse Weaver
Software Developer, LibLime


_______________________________________________
Koha mailing list
[hidden email]
http://lists.katipo.co.nz/mailman/listinfo/koha
Reply | Threaded
Open this post in threaded view
|

Re: Z39.50

Lino Tremblay
In reply to this post by Jesse Weaver-2
Hello Jesse,

I'm receiving this message when I try to search for a record in Z39.50, in the cataloguing module. Weird thing is that I can find records when I change my Z39-50 syntax from MARC21/USMARC to CANMARC, but there's this message instead of the title of each record:

238: Record not available in requested syntax: Available syntax: `Dv, OPAC, USmarc, Danmarc, XML, SUTRS, GRS-1: Bib-1


Lino


Jesse Weaver a écrit :


On Tue, Dec 9, 2008 at 7:16 AM, Lino Tremblay <[hidden email]> wrote:
Hello List,

I'm trying to set up my Z39.50 targets, and I'm sometimes getting this error message:

Koha error

The following fatal error has occurred:

utf8 "\xE2" does not map to Unicode at /usr/lib/perl/5.8/Encode.pm line 166.
Apache Server version: Apache/2.2.3 Server built: Jan 27 2008 18:09:58
Koha 3.00.00.107
Koha DB 3.0000107
MySQL mysql Ver 14.12 Distrib 5.0.32, for pc-linux-gnu (i486) using readline 5.2
OS Linux koha3 2.6.18-6-686 #1 SMP Fri Jun 6 22:22:11 UTC 2008 i686 GNU/Linux
Perl 5.008008


Anybody knows where it's coming from?

Thanks!

Lino

_______________________________________________
Koha mailing list
[hidden email]
http://lists.katipo.co.nz/mailman/listinfo/koha


Is this on the z39.50 target administration page? If so, are there any accented or otherwise not-english characters in the name of the server or any other part of the target?

--
Jesse Weaver
Software Developer, LibLime

-- 
Lino Tremblay, bibliothécaire
Cégep de Sainte-Foy
2410, chemin Sainte-Foy
Québec, Québec
Canada G1V 1T3
Tél.: 418 659-6600, poste 3865
Fax: 418 659-4563

_______________________________________________
Koha mailing list
[hidden email]
http://lists.katipo.co.nz/mailman/listinfo/koha
Reply | Threaded
Open this post in threaded view
|

Re: Z39.50

Lino Tremblay
In reply to this post by Joe Atzberger
Nope, there's not, see by yourself ;)

I use an ISSN for my request, and I know there's more than one record for it.

Lino




Joe Atzberger a écrit :
Specifically, there is apparently one with an "â" character.  I'm not sure why this is causing a crash at this point, but apparently it does. 
--Joe

On Tue, Dec 9, 2008 at 1:33 PM, Jesse Weaver <[hidden email]> wrote:
On Tue, Dec 9, 2008 at 7:16 AM, Lino Tremblay <[hidden email]> wrote:
Hello List,

I'm trying to set up my Z39.50 targets, and I'm sometimes getting this error message:

Koha error

The following fatal error has occurred:

utf8 "\xE2" does not map to Unicode at /usr/lib/perl/5.8/Encode.pm line 166.
Apache Server version: Apache/2.2.3 Server built: Jan 27 2008 18:09:58
Koha MailScanner soupçonne le lien suivant d'être une tentative de fraude de la part de "3.00.00.107" MailScanner warning: numerical links are often malicious: 3.00.00.107
Koha DB 3.0000107
MySQL mysql Ver 14.12 Distrib 5.0.32, for pc-linux-gnu (i486) using readline 5.2
OS Linux koha3 2.6.18-6-686 #1 SMP Fri Jun 6 22:22:11 UTC 2008 i686 GNU/Linux
Perl 5.008008

Anybody knows where it's coming from?

Thanks!

Lino

Is this on the z39.50 target administration page? If so, are there any accented or otherwise not-english characters in the name of the server or any other part of the target?

--
Jesse Weaver
Software Developer, LibLime


-- 
Lino Tremblay, bibliothécaire
Cégep de Sainte-Foy
2410, chemin Sainte-Foy
Québec, Québec
Canada G1V 1T3
Tél.: 418 659-6600, poste 3865
Fax: 418 659-4563

_______________________________________________
Koha mailing list
[hidden email]
http://lists.katipo.co.nz/mailman/listinfo/koha
Reply | Threaded
Open this post in threaded view
|

Locations and sublocations

Lino Tremblay
Hello everybody,

I'm trying to figure out how I'll set up my locations, and I'd like to
know how you guys did. As our situation not atypicall, I'm sure some of
you have faced the same problem

So: we have several collections here, located for the most part in three
places: library, departments and laboratories. Each of these locations
is divided in several sublocations/collections. My problem is that all
locations/sublocations/collections in Koha are at the same level: in an
item, I could choose "Library" as a location, and a specific department
as a sublocation - or the opposite, or any combination I can imagine -
and it would be accepted.

My question now: is there a way to create a hierarchy so that my
Location menu contains only my three locations, and the
Sublocation/collection shows only the collections available within this
location? Or at least refuse an invalid combination?


Thanks!

Lino
_______________________________________________
Koha mailing list
[hidden email]
http://lists.katipo.co.nz/mailman/listinfo/koha
Reply | Threaded
Open this post in threaded view
|

Re: Locations and sublocations

Joann Ransom-2
Hi Lino,

I struggled with this too, and came up with entering 3 locations (which
are physical buildings) and 4 locations (which are collections or
departments within the actual buildings). So 7 altogether, a mixture of
buildings, departments and 'virtual' locations.

Would love to hear other people's solutions as I am still quietly
working through configuration before a data import and still have time
to change..

cheers Jo.



Lino Tremblay wrote:

> Hello everybody,
>
> I'm trying to figure out how I'll set up my locations, and I'd like to
> know how you guys did. As our situation not atypicall, I'm sure some of
> you have faced the same problem
>
> So: we have several collections here, located for the most part in three
> places: library, departments and laboratories. Each of these locations
> is divided in several sublocations/collections. My problem is that all
> locations/sublocations/collections in Koha are at the same level: in an
> item, I could choose "Library" as a location, and a specific department
> as a sublocation - or the opposite, or any combination I can imagine -
> and it would be accepted.
>
> My question now: is there a way to create a hierarchy so that my
> Location menu contains only my three locations, and the
> Sublocation/collection shows only the collections available within this
> location? Or at least refuse an invalid combination?
>
>
> Thanks!
>
> Lino
> _______________________________________________
> Koha mailing list
> [hidden email]
> http://lists.katipo.co.nz/mailman/listinfo/koha
>  

_______________________________________________
Koha mailing list
[hidden email]
http://lists.katipo.co.nz/mailman/listinfo/koha

jransom.vcf (303 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Locations and sublocations

Lino Tremblay
Hello Joann,

One of the problems I see with your solution it your OPAC's Location
menu: it will contain all your locations, sorted alphabetically - which
probably means in no logical order. This is everything but user-friendly
if you have more than 4-5 locations/sublocations... Is it possible to
choose and configure what's in this menu? I'd like to hide some
locations and sublocations, by example.


Lino

Joann Ransom a écrit :

> Hi Lino,
>
> I struggled with this too, and came up with entering 3 locations
> (which are physical buildings) and 4 locations (which are collections
> or departments within the actual buildings). So 7 altogether, a
> mixture of buildings, departments and 'virtual' locations.
>
> Would love to hear other people's solutions as I am still quietly
> working through configuration before a data import and still have time
> to change..
>
> cheers Jo.
>
>
>
> Lino Tremblay wrote:
>> Hello everybody,
>>
>> I'm trying to figure out how I'll set up my locations, and I'd like
>> to know how you guys did. As our situation not atypicall, I'm sure
>> some of you have faced the same problem
>>
>> So: we have several collections here, located for the most part in
>> three places: library, departments and laboratories. Each of these
>> locations is divided in several sublocations/collections. My problem
>> is that all locations/sublocations/collections in Koha are at the
>> same level: in an item, I could choose "Library" as a location, and a
>> specific department as a sublocation - or the opposite, or any
>> combination I can imagine - and it would be accepted.
>>
>> My question now: is there a way to create a hierarchy so that my
>> Location menu contains only my three locations, and the
>> Sublocation/collection shows only the collections available within
>> this location? Or at least refuse an invalid combination?
>>
>>
>> Thanks!
>>
>> Lino
>> _______________________________________________
>> Koha mailing list
>> [hidden email]
>> http://lists.katipo.co.nz/mailman/listinfo/koha
>>  
> _______________________________________________
> Koha mailing list
> [hidden email]
> http://lists.katipo.co.nz/mailman/listinfo/koha
>  

--
Lino Tremblay, bibliothécaire
Cégep de Sainte-Foy
2410, chemin Sainte-Foy
Québec, Québec
Canada G1V 1T3
Tél.: 418 659-6600, poste 3865
Fax: 418 659-4563

_______________________________________________
Koha mailing list
[hidden email]
http://lists.katipo.co.nz/mailman/listinfo/koha
Reply | Threaded
Open this post in threaded view
|

Re: Locations and sublocations

Joann Ransom-2
there you go - that is why I need this forum!

Lino Tremblay wrote:

> Hello Joann,
>
> One of the problems I see with your solution it your OPAC's Location
> menu: it will contain all your locations, sorted alphabetically - which
> probably means in no logical order. This is everything but user-friendly
> if you have more than 4-5 locations/sublocations... Is it possible to
> choose and configure what's in this menu? I'd like to hide some
> locations and sublocations, by example.
>
>
> Lino
>
> Joann Ransom a écrit :
>  
>> Hi Lino,
>>
>> I struggled with this too, and came up with entering 3 locations
>> (which are physical buildings) and 4 locations (which are collections
>> or departments within the actual buildings). So 7 altogether, a
>> mixture of buildings, departments and 'virtual' locations.
>>
>> Would love to hear other people's solutions as I am still quietly
>> working through configuration before a data import and still have time
>> to change..
>>
>> cheers Jo.
>>
>>
>>
>> Lino Tremblay wrote:
>>    
>>> Hello everybody,
>>>
>>> I'm trying to figure out how I'll set up my locations, and I'd like
>>> to know how you guys did. As our situation not atypicall, I'm sure
>>> some of you have faced the same problem
>>>
>>> So: we have several collections here, located for the most part in
>>> three places: library, departments and laboratories. Each of these
>>> locations is divided in several sublocations/collections. My problem
>>> is that all locations/sublocations/collections in Koha are at the
>>> same level: in an item, I could choose "Library" as a location, and a
>>> specific department as a sublocation - or the opposite, or any
>>> combination I can imagine - and it would be accepted.
>>>
>>> My question now: is there a way to create a hierarchy so that my
>>> Location menu contains only my three locations, and the
>>> Sublocation/collection shows only the collections available within
>>> this location? Or at least refuse an invalid combination?
>>>
>>>
>>> Thanks!
>>>
>>> Lino
>>> _______________________________________________
>>> Koha mailing list
>>> [hidden email]
>>> http://lists.katipo.co.nz/mailman/listinfo/koha
>>>  
>>>      
>> _______________________________________________
>> Koha mailing list
>> [hidden email]
>> http://lists.katipo.co.nz/mailman/listinfo/koha
>>  
>>    
>
>  

_______________________________________________
Koha mailing list
[hidden email]
http://lists.katipo.co.nz/mailman/listinfo/koha

jransom.vcf (303 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Locations and sublocations

Lenora Oftedahl
In reply to this post by Lino Tremblay
I would also like to know how to do this.

Thanx

Lenora

>>> Lino Tremblay <[hidden email]> 12/11/2008 12:39 PM >>>
Hello everybody,

I'm trying to figure out how I'll set up my locations, and I'd like to
know how you guys did. As our situation not atypicall, I'm sure some of
you have faced the same problem

So: we have several collections here, located for the most part in three
places: library, departments and laboratories. Each of these locations
is divided in several sublocations/collections. My problem is that all
locations/sublocations/collections in Koha are at the same level: in an
item, I could choose "Library" as a location, and a specific department
as a sublocation - or the opposite, or any combination I can imagine -
and it would be accepted.

My question now: is there a way to create a hierarchy so that my
Location menu contains only my three locations, and the
Sublocation/collection shows only the collections available within this
location? Or at least refuse an invalid combination?


Thanks!

Lino
_______________________________________________
Koha mailing list
[hidden email]
http://lists.katipo.co.nz/mailman/listinfo/koha

_______________________________________________
Koha mailing list
[hidden email]
http://lists.katipo.co.nz/mailman/listinfo/koha
Reply | Threaded
Open this post in threaded view
|

Re: Locations and sublocations

Rachel Hollis
In reply to this post by Lino Tremblay
What I did was create a library for each campus location within the company, then under Authorized Values created locations for separate departments. Fortunately while the company has campus locations in several states, it uses the same terminology for departments within campus locations. The OPAC identifies materials by campus location on search results screens, then within the specific item, which campus department has the item. I made some modifications to locations once I had a few records to evaluate.

Rachel Hollis, librarian
Stevens-Henager College, Boise Idaho Campus

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Lino Tremblay
Sent: Thursday, December 11, 2008 1:40 PM
To: [hidden email]
Subject: [Koha] Locations and sublocations

Hello everybody,

I'm trying to figure out how I'll set up my locations, and I'd like to
know how you guys did. As our situation not atypicall, I'm sure some of
you have faced the same problem

So: we have several collections here, located for the most part in three
places: library, departments and laboratories. Each of these locations
is divided in several sublocations/collections. My problem is that all
locations/sublocations/collections in Koha are at the same level: in an
item, I could choose "Library" as a location, and a specific department
as a sublocation - or the opposite, or any combination I can imagine -
and it would be accepted.

My question now: is there a way to create a hierarchy so that my
Location menu contains only my three locations, and the
Sublocation/collection shows only the collections available within this
location? Or at least refuse an invalid combination?


Thanks!

Lino
_______________________________________________
Koha mailing list
[hidden email]
http://lists.katipo.co.nz/mailman/listinfo/koha


This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
_______________________________________________
Koha mailing list
[hidden email]
http://lists.katipo.co.nz/mailman/listinfo/koha
Reply | Threaded
Open this post in threaded view
|

Re: Locations and sublocations

Kathy Rippel
In reply to this post by Lino Tremblay
If you are talking about the staff use (as opposed to the tech stuff), there is another way of approaching your problem.

I count three (or four) main places in an item records where you can enter hierarchical information that will show up in other places in your catalog that both patrons and staff can see. I would use a combination of these fields to best fit your situation.

I'm a little unsure about the interactions in your scenario about using both Location (952a) and Sublocation (952b). It's possible they could represent your "library, departments and laboratories" and "several sublocations/collections" respectively.

However, if you use your 952a (Location) for your "whatever your institution or entity is", you can subdivide otherwise as follows.

library, departments and laboratories -- these could all be assigned a shelving location (952c)
  • Library
  • Chemistry Dept.
  • Physics Lab
several sublocations/collections -- the next level could be a collection (952 subfield 8).

A further breakdown can be done using the call number (952o)
  • Smith office 628.3
  • Staff Lounge 628.3
Volume numbers and years go best in 952h for us.

Using these areas, you have quite a bit of flexibility, depending on your actual situation.

So, let's take a hypothetical book that is housed in the Chemistry Dept. of "Your Local University Library Collection."

Location: Your Local University Library Collection
Shelving location: Chemistry Dept.
Collection: Faculty offices
Call number: Smith 628.3
Volume: v. 3

I'd cut out the Collection use like this, if you don't need that many levels.

Hope that gives you another perspective.

Kathy
 



 At 02:39 PM 12/11/2008, Lino Tremblay wrote:
Hello everybody,

I'm trying to figure out how I'll set up my locations, and I'd like to
know how you guys did. As our situation not atypicall, I'm sure some of
you have faced the same problem

So: we have several collections here, located for the most part in three
places: library, departments and laboratories. Each of these locations
is divided in several sublocations/collections. My problem is that all
locations/sublocations/collections in Koha are at the same level: in an
item, I could choose "Library" as a location, and a specific department
as a sublocation - or the opposite, or any combination I can imagine -
and it would be accepted.

My question now: is there a way to create a hierarchy so that my
Location menu contains only my three locations, and the
Sublocation/collection shows only the collections available within this
location? Or at least refuse an invalid combination?


Thanks!

Lino
_______________________________________________
Koha mailing list
[hidden email]
http://lists.katipo.co.nz/mailman/listinfo/koha

Kathleen D. Rippel
Pathfinder Central, Manager
Central Kansas Library System
1409 Williams
Great Bend, KS 67530

(620-792-4865) phone
(800-362-2642) toll-free, KS
(620-792-5495) fax

[hidden email]

_______________________________________________
Koha mailing list
[hidden email]
http://lists.katipo.co.nz/mailman/listinfo/koha
Reply | Threaded
Open this post in threaded view
|

Temporary and Home Locations (and sublocations)

Joann Ransom-2
Hi Kathy,

Thank you so much for your well thought out reply. I will use this
method to define the various collections within our branch libraries
when it comes to defining home locations / shelving areas / deweys etc.

I still have a problem though with temporary locations. These include
Foxton Mending Room, Levin Mending Room, Levin Processing Room.

Items may have a brief stint in these transitional 'temporary' or
current locations, while being processed  after acquisitions, or when
needing mending. These temporary locations are not home locations (which
are handled beautifully) in Kathy's example).

How we work it now in Koha 2.9 is that we 'return' items using a scanner
into the appropriate virtual branch (ie Foxton mending or Levin mending
etc). This is quick and means we can find them no matter which mending
room in which town they are at. Likewise, our acquisitions workstation
is set up as Processing branch and all new stock show up with a current
location as Processing.

How will we best achieve this level of functionality in Koha 3.0? I can
only think of creating a Patron for each of these temporary locations,
and then issue items as they are taken into each mending room (for
example) and return them when they are fixed. We really don't want these
transactions counting as 'issues' though for statistical reporting.

Any thoughts?

Cheers Jo Ransom.

Kathy Rippel wrote:

> If you are talking about the staff use (as opposed to the tech stuff),
> there is another way of approaching your problem.
>
> I count three (or four) main places in an item records where you can
> enter hierarchical information that will show up in other places in
> your catalog that both patrons and staff can see. I would use a
> combination of these fields to best fit your situation.
>
> I'm a little unsure about the interactions in your scenario about
> using both Location (952a) and Sublocation (952b). It's possible they
> could represent your "library, departments and laboratories" and
> "several sublocations/collections" respectively.
>
> However, if you use your 952a (Location) for your "whatever your
> institution or entity is", you can subdivide otherwise as follows.
>
> library, departments and laboratories -- these could all be assigned a
> shelving location (952c)
>
>     * Library
>     * Chemistry Dept.
>     * Physics Lab
>
> several sublocations/collections -- the next level could be a
> collection (952 subfield 8).
>
> A further breakdown can be done using the call number (952o)
>
>     * Smith office 628.3
>     * Staff Lounge 628.3
>
> Volume numbers and years go best in 952h for us.
>
> Using these areas, you have quite a bit of flexibility, depending on
> your actual situation.
>
> So, let's take a hypothetical book that is housed in the Chemistry
> Dept. of "Your Local University Library Collection."
>
> Location: Your Local University Library Collection
> Shelving location: Chemistry Dept.
> Collection: Faculty offices
> Call number: Smith 628.3
> Volume: v. 3
>
> I'd cut out the Collection use like this, if you don't need that many
> levels.
>
> Hope that gives you another perspective.
>
> Kathy
>  
>
>
>
>  At 02:39 PM 12/11/2008, Lino Tremblay wrote:
>> Hello everybody,
>>
>> I'm trying to figure out how I'll set up my locations, and I'd like to
>> know how you guys did. As our situation not atypicall, I'm sure some of
>> you have faced the same problem
>>
>> So: we have several collections here, located for the most part in three
>> places: library, departments and laboratories. Each of these locations
>> is divided in several sublocations/collections. My problem is that all
>> locations/sublocations/collections in Koha are at the same level: in an
>> item, I could choose "Library" as a location, and a specific department
>> as a sublocation - or the opposite, or any combination I can imagine -
>> and it would be accepted.
>>
>> My question now: is there a way to create a hierarchy so that my
>> Location menu contains only my three locations, and the
>> Sublocation/collection shows only the collections available within this
>> location? Or at least refuse an invalid combination?
>>
>>
>> Thanks!
>>
>> Lino
>> _______________________________________________
>> Koha mailing list
>> [hidden email]
>> http://lists.katipo.co.nz/mailman/listinfo/koha
>
> Kathleen D. Rippel
> Pathfinder Central, Manager
> Central Kansas Library System
> 1409 Williams
> Great Bend, KS 67530
>
> (620-792-4865) phone
> (800-362-2642) toll-free, KS
> (620-792-5495) fax
>
> [hidden email]
> ------------------------------------------------------------------------
>
> _______________________________________________
> Koha mailing list
> [hidden email]
> http://lists.katipo.co.nz/mailman/listinfo/koha
>  

_______________________________________________
Koha mailing list
[hidden email]
http://lists.katipo.co.nz/mailman/listinfo/koha

jransom.vcf (303 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Temporary and Home Locations (and sublocations)

Joann Ransom-2
Oh, and one thing I forgot to mention, is that 90% of our stock is
circulating stock: with no fixed home location / library. So, 10 % of
the stock has a home location library  ie Foxton, Levin or SHannon, the
other 90% has a home location / library of "Circulating". The ones with
a specified home location must be sent back to their home location no
matter where they are returned to, but the other 90% can be left at
whichever location that the patron cared to return it to.

Cheers Jo.

Joann Ransom wrote:

> Hi Kathy,
>
> Thank you so much for your well thought out reply. I will use this
> method to define the various collections within our branch libraries
> when it comes to defining home locations / shelving areas / deweys etc.
>
> I still have a problem though with temporary locations. These include
> Foxton Mending Room, Levin Mending Room, Levin Processing Room.
>
> Items may have a brief stint in these transitional 'temporary' or
> current locations, while being processed  after acquisitions, or when
> needing mending. These temporary locations are not home locations
> (which are handled beautifully) in Kathy's example).
>
> How we work it now in Koha 2.9 is that we 'return' items using a
> scanner into the appropriate virtual branch (ie Foxton mending or
> Levin mending etc). This is quick and means we can find them no matter
> which mending room in which town they are at. Likewise, our
> acquisitions workstation is set up as Processing branch and all new
> stock show up with a current location as Processing.
>
> How will we best achieve this level of functionality in Koha 3.0? I
> can only think of creating a Patron for each of these temporary
> locations, and then issue items as they are taken into each mending
> room (for example) and return them when they are fixed. We really
> don't want these transactions counting as 'issues' though for
> statistical reporting.
>
> Any thoughts?
>
> Cheers Jo Ransom.
>
> Kathy Rippel wrote:
>> If you are talking about the staff use (as opposed to the tech
>> stuff), there is another way of approaching your problem.
>>
>> I count three (or four) main places in an item records where you can
>> enter hierarchical information that will show up in other places in
>> your catalog that both patrons and staff can see. I would use a
>> combination of these fields to best fit your situation.
>>
>> I'm a little unsure about the interactions in your scenario about
>> using both Location (952a) and Sublocation (952b). It's possible they
>> could represent your "library, departments and laboratories" and
>> "several sublocations/collections" respectively.
>>
>> However, if you use your 952a (Location) for your "whatever your
>> institution or entity is", you can subdivide otherwise as follows.
>>
>> library, departments and laboratories -- these could all be assigned
>> a shelving location (952c)
>>
>>     * Library
>>     * Chemistry Dept.
>>     * Physics Lab
>>
>> several sublocations/collections -- the next level could be a
>> collection (952 subfield 8).
>>
>> A further breakdown can be done using the call number (952o)
>>
>>     * Smith office 628.3
>>     * Staff Lounge 628.3
>>
>> Volume numbers and years go best in 952h for us.
>>
>> Using these areas, you have quite a bit of flexibility, depending on
>> your actual situation.
>>
>> So, let's take a hypothetical book that is housed in the Chemistry
>> Dept. of "Your Local University Library Collection."
>>
>> Location: Your Local University Library Collection
>> Shelving location: Chemistry Dept.
>> Collection: Faculty offices
>> Call number: Smith 628.3
>> Volume: v. 3
>>
>> I'd cut out the Collection use like this, if you don't need that many
>> levels.
>>
>> Hope that gives you another perspective.
>>
>> Kathy
>>  
>>
>>
>>
>>  At 02:39 PM 12/11/2008, Lino Tremblay wrote:
>>> Hello everybody,
>>>
>>> I'm trying to figure out how I'll set up my locations, and I'd like to
>>> know how you guys did. As our situation not atypicall, I'm sure some of
>>> you have faced the same problem
>>>
>>> So: we have several collections here, located for the most part in
>>> three
>>> places: library, departments and laboratories. Each of these locations
>>> is divided in several sublocations/collections. My problem is that all
>>> locations/sublocations/collections in Koha are at the same level: in an
>>> item, I could choose "Library" as a location, and a specific department
>>> as a sublocation - or the opposite, or any combination I can imagine -
>>> and it would be accepted.
>>>
>>> My question now: is there a way to create a hierarchy so that my
>>> Location menu contains only my three locations, and the
>>> Sublocation/collection shows only the collections available within this
>>> location? Or at least refuse an invalid combination?
>>>
>>>
>>> Thanks!
>>>
>>> Lino
>>> _______________________________________________
>>> Koha mailing list
>>> [hidden email]
>>> http://lists.katipo.co.nz/mailman/listinfo/koha
>>
>> Kathleen D. Rippel
>> Pathfinder Central, Manager
>> Central Kansas Library System
>> 1409 Williams
>> Great Bend, KS 67530
>>
>> (620-792-4865) phone
>> (800-362-2642) toll-free, KS
>> (620-792-5495) fax
>>
>> [hidden email]
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Koha mailing list
>> [hidden email]
>> http://lists.katipo.co.nz/mailman/listinfo/koha
>>  
> _______________________________________________
> Koha mailing list
> [hidden email]
> http://lists.katipo.co.nz/mailman/listinfo/koha
>  

_______________________________________________
Koha mailing list
[hidden email]
http://lists.katipo.co.nz/mailman/listinfo/koha

jransom.vcf (303 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Temporary and Home Locations (and sublocations)

Richard Pritsky
In reply to this post by Joann Ransom-2
We have a special patron type for these types of locations--mending, etc.
We then can subtract that patron type from our final issues report.

Hth

Richard Pritsky
Carpenter-Carse Library
Hinesburg, Vermont

-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of Joann Ransom
Sent: Sunday, December 14, 2008 8:49 PM
To: Kathy Rippel
Cc: [hidden email]
Subject: [Koha] Temporary and Home Locations (and sublocations)

Hi Kathy,

Thank you so much for your well thought out reply. I will use this method to
define the various collections within our branch libraries when it comes to
defining home locations / shelving areas / deweys etc.

I still have a problem though with temporary locations. These include Foxton
Mending Room, Levin Mending Room, Levin Processing Room.

Items may have a brief stint in these transitional 'temporary' or current
locations, while being processed  after acquisitions, or when needing
mending. These temporary locations are not home locations (which are handled
beautifully) in Kathy's example).

How we work it now in Koha 2.9 is that we 'return' items using a scanner
into the appropriate virtual branch (ie Foxton mending or Levin mending
etc). This is quick and means we can find them no matter which mending room
in which town they are at. Likewise, our acquisitions workstation is set up
as Processing branch and all new stock show up with a current location as
Processing.

How will we best achieve this level of functionality in Koha 3.0? I can only
think of creating a Patron for each of these temporary locations, and then
issue items as they are taken into each mending room (for
example) and return them when they are fixed. We really don't want these
transactions counting as 'issues' though for statistical reporting.

Any thoughts?

Cheers Jo Ransom.

Kathy Rippel wrote:

> If you are talking about the staff use (as opposed to the tech stuff),
> there is another way of approaching your problem.
>
> I count three (or four) main places in an item records where you can
> enter hierarchical information that will show up in other places in
> your catalog that both patrons and staff can see. I would use a
> combination of these fields to best fit your situation.
>
> I'm a little unsure about the interactions in your scenario about
> using both Location (952a) and Sublocation (952b). It's possible they
> could represent your "library, departments and laboratories" and
> "several sublocations/collections" respectively.
>
> However, if you use your 952a (Location) for your "whatever your
> institution or entity is", you can subdivide otherwise as follows.
>
> library, departments and laboratories -- these could all be assigned a
> shelving location (952c)
>
>     * Library
>     * Chemistry Dept.
>     * Physics Lab
>
> several sublocations/collections -- the next level could be a
> collection (952 subfield 8).
>
> A further breakdown can be done using the call number (952o)
>
>     * Smith office 628.3
>     * Staff Lounge 628.3
>
> Volume numbers and years go best in 952h for us.
>
> Using these areas, you have quite a bit of flexibility, depending on
> your actual situation.
>
> So, let's take a hypothetical book that is housed in the Chemistry
> Dept. of "Your Local University Library Collection."
>
> Location: Your Local University Library Collection Shelving location:
> Chemistry Dept.
> Collection: Faculty offices
> Call number: Smith 628.3
> Volume: v. 3
>
> I'd cut out the Collection use like this, if you don't need that many
> levels.
>
> Hope that gives you another perspective.
>
> Kathy
>  
>
>
>
>  At 02:39 PM 12/11/2008, Lino Tremblay wrote:
>> Hello everybody,
>>
>> I'm trying to figure out how I'll set up my locations, and I'd like
>> to know how you guys did. As our situation not atypicall, I'm sure
>> some of you have faced the same problem
>>
>> So: we have several collections here, located for the most part in
>> three
>> places: library, departments and laboratories. Each of these
>> locations is divided in several sublocations/collections. My problem
>> is that all locations/sublocations/collections in Koha are at the
>> same level: in an item, I could choose "Library" as a location, and a
>> specific department as a sublocation - or the opposite, or any
>> combination I can imagine - and it would be accepted.
>>
>> My question now: is there a way to create a hierarchy so that my
>> Location menu contains only my three locations, and the
>> Sublocation/collection shows only the collections available within
>> this location? Or at least refuse an invalid combination?
>>
>>
>> Thanks!
>>
>> Lino
>> _______________________________________________
>> Koha mailing list
>> [hidden email]
>> http://lists.katipo.co.nz/mailman/listinfo/koha
>
> Kathleen D. Rippel
> Pathfinder Central, Manager
> Central Kansas Library System
> 1409 Williams
> Great Bend, KS 67530
>
> (620-792-4865) phone
> (800-362-2642) toll-free, KS
> (620-792-5495) fax
>
> [hidden email]
> ----------------------------------------------------------------------
> --
>
> _______________________________________________
> Koha mailing list
> [hidden email]
> http://lists.katipo.co.nz/mailman/listinfo/koha
>  

_______________________________________________
Koha mailing list
[hidden email]
http://lists.katipo.co.nz/mailman/listinfo/koha
Reply | Threaded
Open this post in threaded view
|

Re: Temporary and Home Locations (and sublocations)

Joshua Ferraro-3
On Sun, Dec 14, 2008 at 9:13 PM, Richard Pritsky <[hidden email]> wrote:
> We have a special patron type for these types of locations--mending, etc.
> We then can subtract that patron type from our final issues report.
Certainly one way to do it, and you can probably accomplish it best
with a patron of type 'Statistical' so that you can have, for
instance, one at each branch, to further ensure that patron type can
be easily removed from reporting. Statistical patrons also do the
checkout/checkin process in one round trip if that's useful.

Cheers,

Josh

> Hth
>
> Richard Pritsky
> Carpenter-Carse Library
> Hinesburg, Vermont
>
> -----Original Message-----
> From: [hidden email]
> [mailto:[hidden email]] On Behalf Of Joann Ransom
> Sent: Sunday, December 14, 2008 8:49 PM
> To: Kathy Rippel
> Cc: [hidden email]
> Subject: [Koha] Temporary and Home Locations (and sublocations)
>
> Hi Kathy,
>
> Thank you so much for your well thought out reply. I will use this method to
> define the various collections within our branch libraries when it comes to
> defining home locations / shelving areas / deweys etc.
>
> I still have a problem though with temporary locations. These include Foxton
> Mending Room, Levin Mending Room, Levin Processing Room.
>
> Items may have a brief stint in these transitional 'temporary' or current
> locations, while being processed  after acquisitions, or when needing
> mending. These temporary locations are not home locations (which are handled
> beautifully) in Kathy's example).
>
> How we work it now in Koha 2.9 is that we 'return' items using a scanner
> into the appropriate virtual branch (ie Foxton mending or Levin mending
> etc). This is quick and means we can find them no matter which mending room
> in which town they are at. Likewise, our acquisitions workstation is set up
> as Processing branch and all new stock show up with a current location as
> Processing.
>
> How will we best achieve this level of functionality in Koha 3.0? I can only
> think of creating a Patron for each of these temporary locations, and then
> issue items as they are taken into each mending room (for
> example) and return them when they are fixed. We really don't want these
> transactions counting as 'issues' though for statistical reporting.
>
> Any thoughts?
>
> Cheers Jo Ransom.
>
> Kathy Rippel wrote:
>> If you are talking about the staff use (as opposed to the tech stuff),
>> there is another way of approaching your problem.
>>
>> I count three (or four) main places in an item records where you can
>> enter hierarchical information that will show up in other places in
>> your catalog that both patrons and staff can see. I would use a
>> combination of these fields to best fit your situation.
>>
>> I'm a little unsure about the interactions in your scenario about
>> using both Location (952a) and Sublocation (952b). It's possible they
>> could represent your "library, departments and laboratories" and
>> "several sublocations/collections" respectively.
>>
>> However, if you use your 952a (Location) for your "whatever your
>> institution or entity is", you can subdivide otherwise as follows.
>>
>> library, departments and laboratories -- these could all be assigned a
>> shelving location (952c)
>>
>>     * Library
>>     * Chemistry Dept.
>>     * Physics Lab
>>
>> several sublocations/collections -- the next level could be a
>> collection (952 subfield 8).
>>
>> A further breakdown can be done using the call number (952o)
>>
>>     * Smith office 628.3
>>     * Staff Lounge 628.3
>>
>> Volume numbers and years go best in 952h for us.
>>
>> Using these areas, you have quite a bit of flexibility, depending on
>> your actual situation.
>>
>> So, let's take a hypothetical book that is housed in the Chemistry
>> Dept. of "Your Local University Library Collection."
>>
>> Location: Your Local University Library Collection Shelving location:
>> Chemistry Dept.
>> Collection: Faculty offices
>> Call number: Smith 628.3
>> Volume: v. 3
>>
>> I'd cut out the Collection use like this, if you don't need that many
>> levels.
>>
>> Hope that gives you another perspective.
>>
>> Kathy
>>
>>
>>
>>
>>  At 02:39 PM 12/11/2008, Lino Tremblay wrote:
>>> Hello everybody,
>>>
>>> I'm trying to figure out how I'll set up my locations, and I'd like
>>> to know how you guys did. As our situation not atypicall, I'm sure
>>> some of you have faced the same problem
>>>
>>> So: we have several collections here, located for the most part in
>>> three
>>> places: library, departments and laboratories. Each of these
>>> locations is divided in several sublocations/collections. My problem
>>> is that all locations/sublocations/collections in Koha are at the
>>> same level: in an item, I could choose "Library" as a location, and a
>>> specific department as a sublocation - or the opposite, or any
>>> combination I can imagine - and it would be accepted.
>>>
>>> My question now: is there a way to create a hierarchy so that my
>>> Location menu contains only my three locations, and the
>>> Sublocation/collection shows only the collections available within
>>> this location? Or at least refuse an invalid combination?
>>>
>>>
>>> Thanks!
>>>
>>> Lino
>>> _______________________________________________
>>> Koha mailing list
>>> [hidden email]
>>> http://lists.katipo.co.nz/mailman/listinfo/koha
>>
>> Kathleen D. Rippel
>> Pathfinder Central, Manager
>> Central Kansas Library System
>> 1409 Williams
>> Great Bend, KS 67530
>>
>> (620-792-4865) phone
>> (800-362-2642) toll-free, KS
>> (620-792-5495) fax
>>
>> [hidden email]
>> ----------------------------------------------------------------------
>> --
>>
>> _______________________________________________
>> Koha mailing list
>> [hidden email]
>> http://lists.katipo.co.nz/mailman/listinfo/koha
>>
>
> _______________________________________________
> Koha mailing list
> [hidden email]
> http://lists.katipo.co.nz/mailman/listinfo/koha
>



--
Joshua Ferraro                       SUPPORT FOR OPEN-SOURCE SOFTWARE
CEO                         migration, training, maintenance, support
LibLime                                Featuring Koha Open-Source ILS
[hidden email] |Full Demos at http://liblime.com/koha |1(888)KohaILS
_______________________________________________
Koha mailing list
[hidden email]
http://lists.katipo.co.nz/mailman/listinfo/koha
Reply | Threaded
Open this post in threaded view
|

Re: Temporary and Home Locations (and sublocations)

Joann Ransom-2
Thanks Joshua,

I discovered that Statistical category of members yesterday and it looks
like the way to go - will continue playing!

cheers Jo.

Joshua Ferraro wrote:

> On Sun, Dec 14, 2008 at 9:13 PM, Richard Pritsky <[hidden email]> wrote:
>  
>> We have a special patron type for these types of locations--mending, etc.
>> We then can subtract that patron type from our final issues report.
>>    
> Certainly one way to do it, and you can probably accomplish it best
> with a patron of type 'Statistical' so that you can have, for
> instance, one at each branch, to further ensure that patron type can
> be easily removed from reporting. Statistical patrons also do the
> checkout/checkin process in one round trip if that's useful.
>
> Cheers,
>
> Josh
>
>  
>> Hth
>>
>> Richard Pritsky
>> Carpenter-Carse Library
>> Hinesburg, Vermont
>>
>> -----Original Message-----
>> From: [hidden email]
>> [mailto:[hidden email]] On Behalf Of Joann Ransom
>> Sent: Sunday, December 14, 2008 8:49 PM
>> To: Kathy Rippel
>> Cc: [hidden email]
>> Subject: [Koha] Temporary and Home Locations (and sublocations)
>>
>> Hi Kathy,
>>
>> Thank you so much for your well thought out reply. I will use this method to
>> define the various collections within our branch libraries when it comes to
>> defining home locations / shelving areas / deweys etc.
>>
>> I still have a problem though with temporary locations. These include Foxton
>> Mending Room, Levin Mending Room, Levin Processing Room.
>>
>> Items may have a brief stint in these transitional 'temporary' or current
>> locations, while being processed  after acquisitions, or when needing
>> mending. These temporary locations are not home locations (which are handled
>> beautifully) in Kathy's example).
>>
>> How we work it now in Koha 2.9 is that we 'return' items using a scanner
>> into the appropriate virtual branch (ie Foxton mending or Levin mending
>> etc). This is quick and means we can find them no matter which mending room
>> in which town they are at. Likewise, our acquisitions workstation is set up
>> as Processing branch and all new stock show up with a current location as
>> Processing.
>>
>> How will we best achieve this level of functionality in Koha 3.0? I can only
>> think of creating a Patron for each of these temporary locations, and then
>> issue items as they are taken into each mending room (for
>> example) and return them when they are fixed. We really don't want these
>> transactions counting as 'issues' though for statistical reporting.
>>
>> Any thoughts?
>>
>> Cheers Jo Ransom.
>>
>> Kathy Rippel wrote:
>>    
>>> If you are talking about the staff use (as opposed to the tech stuff),
>>> there is another way of approaching your problem.
>>>
>>> I count three (or four) main places in an item records where you can
>>> enter hierarchical information that will show up in other places in
>>> your catalog that both patrons and staff can see. I would use a
>>> combination of these fields to best fit your situation.
>>>
>>> I'm a little unsure about the interactions in your scenario about
>>> using both Location (952a) and Sublocation (952b). It's possible they
>>> could represent your "library, departments and laboratories" and
>>> "several sublocations/collections" respectively.
>>>
>>> However, if you use your 952a (Location) for your "whatever your
>>> institution or entity is", you can subdivide otherwise as follows.
>>>
>>> library, departments and laboratories -- these could all be assigned a
>>> shelving location (952c)
>>>
>>>     * Library
>>>     * Chemistry Dept.
>>>     * Physics Lab
>>>
>>> several sublocations/collections -- the next level could be a
>>> collection (952 subfield 8).
>>>
>>> A further breakdown can be done using the call number (952o)
>>>
>>>     * Smith office 628.3
>>>     * Staff Lounge 628.3
>>>
>>> Volume numbers and years go best in 952h for us.
>>>
>>> Using these areas, you have quite a bit of flexibility, depending on
>>> your actual situation.
>>>
>>> So, let's take a hypothetical book that is housed in the Chemistry
>>> Dept. of "Your Local University Library Collection."
>>>
>>> Location: Your Local University Library Collection Shelving location:
>>> Chemistry Dept.
>>> Collection: Faculty offices
>>> Call number: Smith 628.3
>>> Volume: v. 3
>>>
>>> I'd cut out the Collection use like this, if you don't need that many
>>> levels.
>>>
>>> Hope that gives you another perspective.
>>>
>>> Kathy
>>>
>>>
>>>
>>>
>>>  At 02:39 PM 12/11/2008, Lino Tremblay wrote:
>>>      
>>>> Hello everybody,
>>>>
>>>> I'm trying to figure out how I'll set up my locations, and I'd like
>>>> to know how you guys did. As our situation not atypicall, I'm sure
>>>> some of you have faced the same problem
>>>>
>>>> So: we have several collections here, located for the most part in
>>>> three
>>>> places: library, departments and laboratories. Each of these
>>>> locations is divided in several sublocations/collections. My problem
>>>> is that all locations/sublocations/collections in Koha are at the
>>>> same level: in an item, I could choose "Library" as a location, and a
>>>> specific department as a sublocation - or the opposite, or any
>>>> combination I can imagine - and it would be accepted.
>>>>
>>>> My question now: is there a way to create a hierarchy so that my
>>>> Location menu contains only my three locations, and the
>>>> Sublocation/collection shows only the collections available within
>>>> this location? Or at least refuse an invalid combination?
>>>>
>>>>
>>>> Thanks!
>>>>
>>>> Lino
>>>> _______________________________________________
>>>> Koha mailing list
>>>> [hidden email]
>>>> http://lists.katipo.co.nz/mailman/listinfo/koha
>>>>        
>>> Kathleen D. Rippel
>>> Pathfinder Central, Manager
>>> Central Kansas Library System
>>> 1409 Williams
>>> Great Bend, KS 67530
>>>
>>> (620-792-4865) phone
>>> (800-362-2642) toll-free, KS
>>> (620-792-5495) fax
>>>
>>> [hidden email]
>>> ----------------------------------------------------------------------
>>> --
>>>
>>> _______________________________________________
>>> Koha mailing list
>>> [hidden email]
>>> http://lists.katipo.co.nz/mailman/listinfo/koha
>>>
>>>      
>> _______________________________________________
>> Koha mailing list
>> [hidden email]
>> http://lists.katipo.co.nz/mailman/listinfo/koha
>>
>>    
>
>
>
>  

_______________________________________________
Koha mailing list
[hidden email]
http://lists.katipo.co.nz/mailman/listinfo/koha

jransom.vcf (303 bytes) Download Attachment