Numeric subfield in framework
I'm editing subtags in a MARC21 framework, and trying to use 302.a for book's pages number. At Tag subfield structure -> Edit -> Other options; how can I set authorized value to be only a positive integer number? Thanks.
On 2018-03-16 06:00 AM, Narcis Garcia wrote:
I'm editing subtags in a MARC21 framework, and trying to use 302.a for book's pages number. At Tag subfield structure -> Edit -> Other options; how can I set authorized value to be only a positive integer number?
Javascript *might* allow you to limit to 'a positive integer', but why? First, tag 302 is obsolete (so LoC, if you accept them as properly reflecting MARC21 status, do not supply suggestions.) Secondly, the number of pages in a bibliographic record are normally recorded in 300$a - "Extent", described as "Number of physical pages, volumes, cassettes, total playing time, etc., of of each type of unit." We often have entries such as: 300 ##$axii, 352, [8 advert.] p. LoC <http://www.loc.gov/marc/bibliographic/bd300.html> give additional examples such as: 300 ##$a1 videocassette of 1 (Beta) (30 min.) which might answer your follow-up email. Best -- Paul
Thanks; I didn't see tag 300.a Applying replacement. About JavaScript, let's see how can it be implemented consistently in Koha. I'm really surprised Koha seems not having implemented data types (numeric, boolean, string, binary, date/time...). El 16/03/18 a les 15:31, Paul A ha escrit:
On 2018-03-16 06:00 AM, Narcis Garcia wrote:
I'm editing subtags in a MARC21 framework, and trying to use 302.a for book's pages number. At Tag subfield structure -> Edit -> Other options; how can I set authorized value to be only a positive integer number?
Javascript *might* allow you to limit to 'a positive integer', but why?
First, tag 302 is obsolete (so LoC, if you accept them as properly reflecting MARC21 status, do not supply suggestions.)
Secondly, the number of pages in a bibliographic record are normally recorded in 300$a - "Extent", described as "Number of physical pages, volumes, cassettes, total playing time, etc., of of each type of unit."
We often have entries such as: 300 ##$axii, 352, [8 advert.] p.
LoC <http://www.loc.gov/marc/bibliographic/bd300.html> give additional examples such as: 300 ##$a1 videocassette of 1 (Beta) (30 min.)
which might answer your follow-up email.
Best -- Paul
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
On 2018-03-16 10:59 AM, Narcis Garcia wrote:
Thanks; I didn't see tag 300.a
It's a standard bibliographic entry for cataloguing, used by all major libraries.
Applying replacement. About JavaScript, let's see how can it be implemented consistently in Koha.
I'm really surprised Koha seems not having implemented data types (numeric, boolean, string, binary, date/time...).
Koha *does* implement data types, where required by cataloguing rules and conventions (and by internal db constraints.) Tag 300$a is *not* an integer by any stretch of anybody's imagination. This list is here to help you. You might like to explain which version of Koha you are implementing, and which library you are working for. That would assist the Koha community in giving you the best possible advice. You give the impression (y disculpame si estoy en error) that you have done very little MARC cataloguing. I might suggest that you look at records from Library of Congress, the British Library, Library Archives Canada, etc. particularly via Z39.50, or through the web interface to WorldCat (OCLC). Koha is very good at "compliance" -- but does allow flexibility for you to go off on a tangent and "reinvent the wheel" if you have "non-industry / non-professional / specialized / amateur" requirements. Amicalmente -- Paul
El 16/03/18 a les 15:31, Paul A ha escrit:
On 2018-03-16 06:00 AM, Narcis Garcia wrote:
I'm editing subtags in a MARC21 framework, and trying to use 302.a for book's pages number. At Tag subfield structure -> Edit -> Other options; how can I set authorized value to be only a positive integer number?
Javascript *might* allow you to limit to 'a positive integer', but why?
First, tag 302 is obsolete (so LoC, if you accept them as properly reflecting MARC21 status, do not supply suggestions.)
Secondly, the number of pages in a bibliographic record are normally recorded in 300$a - "Extent", described as "Number of physical pages, volumes, cassettes, total playing time, etc., of of each type of unit."
We often have entries such as: 300 ##$axii, 352, [8 advert.] p.
LoC <http://www.loc.gov/marc/bibliographic/bd300.html> give additional examples such as: 300 ##$a1 videocassette of 1 (Beta) (30 min.)
which might answer your follow-up email.
Best -- Paul
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
El 16/03/18 a les 18:35, Paul A ha escrit:
On 2018-03-16 10:59 AM, Narcis Garcia wrote:
Thanks; I didn't see tag 300.a
It's a standard bibliographic entry for cataloguing, used by all major libraries.
Applying replacement. About JavaScript, let's see how can it be implemented consistently in Koha.
I'm really surprised Koha seems not having implemented data types (numeric, boolean, string, binary, date/time...).
Koha *does* implement data types, where required by cataloguing rules and conventions (and by internal db constraints.) Tag 300$a is *not* an integer by any stretch of anybody's imagination.
This list is here to help you. You might like to explain which version of Koha you are implementing, and which library you are working for. That would assist the Koha community in giving you the best possible advice.
You give the impression (y disculpame si estoy en error) that you have done very little MARC cataloguing. I might suggest that you look at records from Library of Congress, the British Library, Library Archives Canada, etc. particularly via Z39.50, or through the web interface to WorldCat (OCLC). Koha is very good at "compliance" -- but does allow flexibility for you to go off on a tangent and "reinvent the wheel" if you have "non-industry / non-professional / specialized / amateur" requirements.
Amicalmente -- Paul
I've installed Koha 17.11 and I'm not implied in calaloguing but in computing. I'm trying to setup bibliographic software in a small library, with the double hope: catalogue is viewable publicly from internet and other libraries in the same association can join with their catalogs. I've not found any other easier CMS (translated to spanish) with those 2 features I hope to deploy. I feel koha seems so open and flexible that it needs x10 documentation and examples than now (and current resources are really big and great!)
Narcis, you could consider joining us at koha-es (Yahoo groups). And of course make your librarians join too! El vie., 16 mar. 2018 a las 15:40, Narcis Garcia (<informatica@actiu.net>) escribió:
El 16/03/18 a les 18:35, Paul A ha escrit:
On 2018-03-16 10:59 AM, Narcis Garcia wrote:
Thanks; I didn't see tag 300.a
It's a standard bibliographic entry for cataloguing, used by all major libraries.
Applying replacement. About JavaScript, let's see how can it be implemented consistently in Koha.
I'm really surprised Koha seems not having implemented data types (numeric, boolean, string, binary, date/time...).
Koha *does* implement data types, where required by cataloguing rules and conventions (and by internal db constraints.) Tag 300$a is *not* an integer by any stretch of anybody's imagination.
This list is here to help you. You might like to explain which version of Koha you are implementing, and which library you are working for. That would assist the Koha community in giving you the best possible advice.
You give the impression (y disculpame si estoy en error) that you have done very little MARC cataloguing. I might suggest that you look at records from Library of Congress, the British Library, Library Archives Canada, etc. particularly via Z39.50, or through the web interface to WorldCat (OCLC). Koha is very good at "compliance" -- but does allow flexibility for you to go off on a tangent and "reinvent the wheel" if you have "non-industry / non-professional / specialized / amateur" requirements.
Amicalmente -- Paul
I've installed Koha 17.11 and I'm not implied in calaloguing but in computing. I'm trying to setup bibliographic software in a small library, with the double hope: catalogue is viewable publicly from internet and other libraries in the same association can join with their catalogs.
I've not found any other easier CMS (translated to spanish) with those 2 features I hope to deploy. I feel koha seems so open and flexible that it needs x10 documentation and examples than now (and current resources are really big and great!) _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F
I'm sorry and thanks; I don't subscribe third-party services (including Yahoo/google/etc contract). I really prefer FOSS and neutral tools. As small libraries I meant less than a thousand books each one (and volunteers dedicating few hours per month), and I'm facing a tool (Koha) designed for really big libraries and with dedicated professionals. El 16/03/18 a les 19:45, Tomas Cohen Arazi ha escrit:
Narcis, you could consider joining us at koha-es (Yahoo groups). And of course make your librarians join too!
El vie., 16 mar. 2018 a las 15:40, Narcis Garcia (<informatica@actiu.net <mailto:informatica@actiu.net>>) escribió:
El 16/03/18 a les 18:35, Paul A ha escrit: > On 2018-03-16 10:59 AM, Narcis Garcia wrote: >> Thanks; I didn't see tag 300.a > > It's a standard bibliographic entry for cataloguing, used by all major > libraries. > >> Applying replacement. >> About JavaScript, let's see how can it be implemented consistently in >> Koha. >> >> I'm really surprised Koha seems not having implemented data types >> (numeric, boolean, string, binary, date/time...). > > Koha *does* implement data types, where required by cataloguing rules > and conventions (and by internal db constraints.) Tag 300$a is *not* an > integer by any stretch of anybody's imagination. > > This list is here to help you. You might like to explain which version > of Koha you are implementing, and which library you are working for. > That would assist the Koha community in giving you the best possible > advice. > > You give the impression (y disculpame si estoy en error) that you have > done very little MARC cataloguing. I might suggest that you look at > records from Library of Congress, the British Library, Library Archives > Canada, etc. particularly via Z39.50, or through the web interface to > WorldCat (OCLC). Koha is very good at "compliance" -- but does allow > flexibility for you to go off on a tangent and "reinvent the wheel" if > you have "non-industry / non-professional / specialized / amateur" > requirements. > > Amicalmente -- Paul > >
I've installed Koha 17.11 and I'm not implied in calaloguing but in computing. I'm trying to setup bibliographic software in a small library, with the double hope: catalogue is viewable publicly from internet and other libraries in the same association can join with their catalogs.
I've not found any other easier CMS (translated to spanish) with those 2 features I hope to deploy. I feel koha seems so open and flexible that it needs x10 documentation and examples than now (and current resources are really big and great!) _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz> https://lists.katipo.co.nz/mailman/listinfo/koha
-- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F
Ha! I will use it (again) in my tenth attempt to move the list to @ koha-community.org Thanks! Regarding Koha on big libraries, as a support vendor I can tell Koha suits both tiny libraires and big consortia. I've helped myself several small libraries get up and running. After that, some care for the tool maintenance is all that's needed. And we love to help here with issues that arise, and for more synchronous conversations on IRC. Have nice weekend! El vie., 16 mar. 2018 a las 15:52, Narcis Garcia (<informatica@actiu.net>) escribió:
I'm sorry and thanks; I don't subscribe third-party services (including Yahoo/google/etc contract). I really prefer FOSS and neutral tools.
As small libraries I meant less than a thousand books each one (and volunteers dedicating few hours per month), and I'm facing a tool (Koha) designed for really big libraries and with dedicated professionals.
Narcis, you could consider joining us at koha-es (Yahoo groups). And of course make your librarians join too!
El vie., 16 mar. 2018 a las 15:40, Narcis Garcia (<informatica@actiu.net <mailto:informatica@actiu.net>>) escribió:
El 16/03/18 a les 18:35, Paul A ha escrit: > On 2018-03-16 10:59 AM, Narcis Garcia wrote: >> Thanks; I didn't see tag 300.a > > It's a standard bibliographic entry for cataloguing, used by all major > libraries. > >> Applying replacement. >> About JavaScript, let's see how can it be implemented consistently in >> Koha. >> >> I'm really surprised Koha seems not having implemented data types >> (numeric, boolean, string, binary, date/time...). > > Koha *does* implement data types, where required by cataloguing rules > and conventions (and by internal db constraints.) Tag 300$a is *not* an > integer by any stretch of anybody's imagination. > > This list is here to help you. You might like to explain which version > of Koha you are implementing, and which library you are working for. > That would assist the Koha community in giving you the best
El 16/03/18 a les 19:45, Tomas Cohen Arazi ha escrit: possible
> advice. > > You give the impression (y disculpame si estoy en error) that you
have
> done very little MARC cataloguing. I might suggest that you look at > records from Library of Congress, the British Library, Library Archives > Canada, etc. particularly via Z39.50, or through the web interface
to
> WorldCat (OCLC). Koha is very good at "compliance" -- but does
allow
> flexibility for you to go off on a tangent and "reinvent the
wheel" if
> you have "non-industry / non-professional / specialized / amateur" > requirements. > > Amicalmente -- Paul > >
I've installed Koha 17.11 and I'm not implied in calaloguing but in computing. I'm trying to setup bibliographic software in a small library, with
the
double hope: catalogue is viewable publicly from internet and other libraries in the same association can join with their catalogs.
I've not found any other easier CMS (translated to spanish) with
those 2
features I hope to deploy. I feel koha seems so open and flexible that it needs x10
documentation
and examples than now (and current resources are really big and
great!)
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz> https://lists.katipo.co.nz/mailman/listinfo/koha
-- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 <+54%209%20351%20351-3384> GPG: B2F3C15F
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F
participants (3)
-
Narcis Garcia -
Paul A -
Tomas Cohen Arazi