[OPEN-ILS-GENERAL] ***SPAM*** Re: Open-ils-general Digest, Vol 53, Issue 13
chigwagwap at msu.ac.zw
chigwagwap at msu.ac.zw
Mon Nov 8 09:53:05 EST 2010
hie
yes ejabberd is starting
here is ejabbererd.conf
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
%%%
%%% Debian ejabberd configuration file
%%% This config must be in UTF-8 encoding
%%%
%%% The parameters used in this configuration file are explained in
more detail
%%% in the ejabberd Installation and Operation Guide.
%%% Please consult the Guide in case of doubts, it is available at
%%% /usr/share/doc/ejabberd/guide.html
%%% ===================================
%%% OVERRIDE OPTIONS STORED IN DATABASE
%%
%% Override global options (shared by all ejabberd nodes in a cluster).
%%
%%override_global.
%%
%% Override local options (specific for this particular ejabberd node).
%%
%%
%%override_local.
%%override_local.
%%
%% Remove the Access Control Lists before new ones are added.
%%
%%override_acls.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%% Options which are set by Debconf and managed by ucf
%% Admin user
{acl, admin, {user, "", "localhost"}}.
%% Hostname
%%{hosts, ["localhost"]}.
{hosts, ["loclahosts", "private.localhost", "public.localhost"}.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%% This configuration file contains Erlang terms.
%%% In case you want to understand the syntax, here are the concepts:
%%%
%%% - The character to comment a line is %
%%%
%%% - Each term ends in a dot, for example:
%%% override_global.
%%%
%%% - A tuple has a fixed definition, its elements are
%%% enclosed in {}, and separated with commas:
%%% {loglevel, 4}.
%%%
%%% - A list can have as many elements as you want,
%%% and is enclosed in [], for example:
%%% [http_poll, web_admin, tls]
%%%
%%% - A keyword of ejabberd is a word in lowercase.
%%% The strings are enclosed in "" and can have spaces, dots...
%%% {language, "en"}.
%%% {ldap_rootdn, "dc=example,dc=com"}.
%%%
%%% - This term includes a tuple, a keyword, a list and two strings:
%%% {hosts, ["jabber.example.net", "im.example.com"]}.
%%%
%%% =========
%%% DEBUGGING
%%
%% loglevel: Verbosity of log files generated by ejabberd.
%% 0: No ejabberd log at all (not recommended)
%% 1: Critical
%% 2: Error
%% 3: Warning
%% 4: Info
%% 5: Debug
%%
{loglevel, 4}.
%%
%% watchdog_admins: If an ejabberd process consumes too much memory,
%% send live notifications to those Jabber accounts.
%%
%%{watchdog_admins, ["bob at example.com"]}.
%%% ================
%%% SERVED HOSTNAMES
%%
%% hosts: Domains served by ejabberd.
%% You can define one or several, for example:
%% {hosts, ["example.net", "example.com", "example.org"]}.
%%
%% (This option is defined by debconf earlier)
%% {hosts, ["localhost"]}.
%%
%% route_subdomains: Delegate subdomains to other Jabber server.
%% For example, if this ejabberd serves example.org and you want
%% to allow communication with a Jabber server called im.example.org.
%%
%%{route_subdomains, s2s}.
%%% ===============
%%% LISTENING PORTS
%%
%% listen: Which ports will ejabberd listen, which service handles it
%% and what options to start it with.
%%
{listen,
[
{5222, ejabberd_c2s, [
{access, c2s},
{shaper, c2s_shaper},
{max_stanza_size, 2000000},
starttls, {certfile, "/etc/ejabberd/ejabberd.pem"}
]},
%%
%% To enable the old SSL connection method (deprecated) in port 5223:
%%
%%{5223, ejabberd_c2s, [
%% {access, c2s},
%% {shaper, c2s_shaper},
%% {max_stanza_size, 2000000},
%% tls, {certfile, "/etc/ejabberd/ejabberd.pem"}
%% ]},
{5269, ejabberd_s2s_in, [
{shaper, s2s_shaper},
{max_stanza_size, 2000000}
]},
%% External MUC jabber-muc (but internal mod_muc is better :))
%%{5554, ejabberd_service, [
%% {ip, {127, 0, 0, 1}},
%% {access, all},
%% {shaper_rule, fast},
%% {host, "muc.localhost", [{password, "secret"}]}
%% ]},
%% Jabber ICQ Transport
%%{5555, ejabberd_service, [
%% {ip, {127, 0, 0, 1}},
%% {access, all},
%% {shaper_rule, fast},
%% {hosts, ["icq.localhost", "sms.localhost"],
%% [{password, "secret"}]}
%% ]},
%% AIM Transport
%%{5556, ejabberd_service, [
%% {ip, {127, 0, 0, 1}},
%% {access, all},
%% {shaper_rule, fast},
%% {host, "aim.localhost", [{password, "secret"}]}
%% ]},
%% MSN Transport
%%{5557, ejabberd_service, [
%% {ip, {127, 0, 0, 1}},
%% {access, all},
%% {shaper_rule, fast},
%% {host, "msn.localhost", [{password, "secret"}]}
%% ]},
%% Yahoo! Transport
%%{5558, ejabberd_service, [
%% {ip, {127, 0, 0, 1}},
%% {access, all},
%% {shaper_rule, fast},
%% {host, "yahoo.localhost", [{password, "secret"}]}
%% ]},
%% External JUD (internal is more powerful,
%% but doesn't allow to register users from other servers)
%%{5559, ejabberd_service, [
%% {ip, {127, 0, 0, 1}},
%% {access, all},
%% {shaper_rule, fast},
%% {host, "jud.localhost", [{password, "secret"}]}
%% ]},
{5280, ejabberd_http, [
http_poll,
web_admin
]}
]}.
%%
%% s2s_use_starttls: Enable STARTTLS + Dialback for S2S connections.
%% Allowed values are: true or false.
%% You must specify a certificate file.
%%
{s2s_use_starttls, true}.
%%
%% s2s_certfile: Specify a certificate file.
%%
{s2s_certfile, "/etc/ejabberd/ejabberd.pem"}.
%%
%% domain_certfile: Specify a different certificate for each served hostname.
%%
%%{domain_certfile, "example.org", "/path/to/example_org.pem"}.
%%{domain_certfile, "example.com", "/path/to/example_com.pem"}.
%%
%% S2S whitelist or blacklist
%%
%% Default s2s policy for undefined hosts.
%%
%%{s2s_default_policy, allow}.
%%
%% Allow or deny communication with specific servers.
%%
%%{{s2s_host, "goodhost.org"}, allow}.
%%{{s2s_host, "badhost.org"}, deny}.
%%% ==============
%%% AUTHENTICATION
%%
%% auth_method: Method used to authenticate the users.
%% The default method is the internal.
%% If you want to use a different method,
%% comment this line and enable the correct ones.
%%
{auth_method, internal}.
%%
%% Authentication using external script
%% Make sure the script is executable by ejabberd.
%%
%%{auth_method, external}.
%%{extauth_program, "/path/to/authentication/script"}.
%%
%% Authentication using ODBC
%% Remember to setup a database in the next section.
%%
%%{auth_method, odbc}.
%%
%% Authentication using PAM
%%
%%{auth_method, pam}.
%%{pam_service, "pamservicename"}.
%%
%% Authentication using LDAP
%%
%%{auth_method, ldap}.
%%
%% List of LDAP servers:
%%{ldap_servers, ["localhost"]}.
%%
%% Encryption of connection to LDAP servers (LDAPS):
%%{ldap_encrypt, tls}.
%%
%% Port connect to LDAP server:
%%{ldap_port, 636}.
%%
%% LDAP manager:
%%{ldap_rootdn, "dc=example,dc=com"}.
%%
%% Password to LDAP manager:
%%{ldap_password, "******"}.
%%
%% Search base of LDAP directory:
%%{ldap_base, "dc=example,dc=com"}.
%%
%% LDAP attribute that holds user ID:
%%{ldap_uids, [{"mail", "%u at mail.example.org"}]}.
%%
%% LDAP filter:
%%{ldap_filter, "(objectClass=shadowAccount)"}.
%%
%% Anonymous login support:
%% auth_method: anonymous
%% anonymous_protocol: sasl_anon | login_anon | both
%% allow_multiple_connections: true | false
%%
%%{host_config, "public.example.org", [{auth_method, anonymous},
%% {allow_multiple_connections, false},
%% {anonymous_protocol, sasl_anon}]}.
%%
%% To use both anonymous and internal authentication:
%%
%%{host_config, "public.example.org", [{auth_method, [internal, anonymous]}]}.
%%% ==============
%%% DATABASE SETUP
%% ejabberd uses by default the internal Mnesia database,
%% so you can avoid this section.
%% This section provides configuration examples in case
%% you want to use other database backends.
%% Please consult the ejabberd Guide for details about database creation.
%%
%% MySQL server:
%%
%%{odbc_server, {mysql, "server", "database", "username", "password"}}.
%%
%% If you want to specify the port:
%%{odbc_server, {mysql, "server", 1234, "database", "username", "password"}}.
%%
%% PostgreSQL server:
%%
%%{odbc_server, {pgsql, "server", "database", "username", "password"}}.
%%
%% If you want to specify the port:
%%{odbc_server, {pgsql, "server", 1234, "database", "username", "password"}}.
%%
%% If you use PostgreSQL, have a large database, and need a
%% faster but inexact replacement for "select count(*) from users"
%%
%%{pgsql_users_number_estimate, true}.
%%
%% ODBC compatible or MSSQL server:
%%
%%{odbc_server, "DSN=ejabberd;UID=ejabberd;PWD=ejabberd"}.
%%
%% Number of connections to open to the database for each virtual host
%%
%%{odbc_pool_size, 10}.
%%
%% Interval to make a dummy SQL request to keep alive the connections
%% to the database. Specify in seconds: for example 28800 means 8 hours
%%
%%{odbc_keepalive_interval, undefined}.
%%% ===============
%%% TRAFFIC SHAPERS
%%
%% The "normal" shaper limits traffic speed to 1.000 B/s
%%
{shaper, normal, {maxrate, 500000}}.
%%
%% The "fast" shaper limits traffic speed to 50.000 B/s
%%
{shaper, fast, {maxrate, 50000}}.
%%% ====================
%%% ACCESS CONTROL LISTS
%%
%% The 'admin' ACL grants administrative privileges to Jabber accounts.
%% You can put as many accounts as you want.
%%
%%{acl, admin, {user, "aleksey", "localhost"}}.
%%{acl, admin, {user, "ermine", "example.org"}}.
%%
%% Blocked users
%%
%%{acl, blocked, {user, "baduser", "example.org"}}.
%%{acl, blocked, {user, "test"}}.
%%
%% Local users: don't modify this line.
%%
{acl, local, {user_regexp, ""}}.
%%
%% More examples of ACLs
%%
%%{acl, jabberorg, {server, "jabber.org"}}.
%%{acl, aleksey, {user, "aleksey", "jabber.ru"}}.
%%{acl, test, {user_regexp, "^test"}}.
%%{acl, test, {user_glob, "test*"}}.
%%% ============
%%% ACCESS RULES
%% Define the maximum number of time a single user is allowed to connect:
{access, max_user_sessions, [{10000, all}]}.
%% This rule allows access only for local users:
{access, local, [{allow, local}]}.
%% Only non-blocked users can use c2s connections:
{access, c2s, [{deny, blocked},
{allow, all}]}.
%% For all users except admins used "normal" shaper
{access, c2s_shaper, [{none, admin},
{normal, all}]}.
%% For all S2S connections used "fast" shaper
{access, s2s_shaper, [{fast, all}]}.
%% Only admins can send announcement messages:
{access, announce, [{allow, admin}]}.
%% Only admins can use configuration interface:
{access, configure, [{allow, admin}]}.
%% Admins of this server are also admins of MUC service:
{access, muc_admin, [{allow, admin}]}.
%% All users are allowed to use MUC service:
{access, muc, [{allow, all}]}.
%% No username can be registered via in-band registration:
%% To enable in-band registration, replace 'deny' with 'allow'
% (note that if you remove mod_register from modules list then users will not
% be able to change their password as well as register).
% This setting is default because it's more safe.
{access, register, [{deny, all}]}.
%% Everybody can create pubsub nodes
{access, pubsub_createnode, [{allow, all}]}.
%%% ================
%%% DEFAULT LANGUAGE
%%
%% language: Default language used for server messages.
%%
{language, "en"}.
%%% =======
%%% MODULES
%%
%% Modules enabled in all ejabberd virtual hosts.
%%
{modules,
[
{mod_adhoc, []},
{mod_announce, [{access, announce}]}, % requires mod_adhoc
{mod_caps, []},
{mod_configure,[]}, % requires mod_adhoc
{mod_ctlextra, []},
{mod_disco, []},
%%{mod_echo, [{host, "echo.localhost"}]},
{mod_irc, []},
{mod_last, []},
{mod_muc, [
%%{host, "conference. at HOST@"},
{access, muc},
{access_create, muc},
{access_persistent, muc},
{access_admin, muc_admin},
{max_users, 500}
]},
%%{mod_muc_log,[]},
%%{mod_offline, []},
{mod_privacy, []},
{mod_private, []},
{mod_proxy65, [
{access, local},
{shaper, c2s_shaper}
]},
{mod_pubsub, [ % requires mod_caps
{access_createnode, pubsub_createnode},
{plugins, ["default", "pep"]}
]},
{mod_register, [
%%
%% After successful registration, the user receives
%% a message with this subject and body.
%%
{welcome_message, {"Welcome!",
"Welcome to a Jabber service
powered by Debian. "
"For information about Jabber visit "
"http://www.jabber.org"}},
%% Replace it with 'none' if you don't want to send
such message:
%%{welcome_message, none},
%%
%% When a user registers, send a notification to
%% these Jabber accounts.
%%
%%{registration_watchers, ["admin1 at example.org"]},
{access, register}
]},
{mod_roster, []},
%%{mod_service_log,[]},
%%{mod_shared_roster,[]},
{mod_stats, []},
{mod_time, []},
{mod_vcard, []},
{mod_version, []}
]}.
%%% $Id: ejabberd.cfg.example 1178 2008-02-08 18:28:36Z badlop $
%%% Local Variables:
%%% mode: erlang
%%% End:
###############################################################################
hosts file
127.0.0.1 localhost
127.0.1.1 ubuntu.libserver ubuntu
127.0.1.2 public.localhost public
127.0.1.3 private.localhost private
# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
~
##############################################################################
Quoting open-ils-general-request at list.georgialibraries.org:
> Send Open-ils-general mailing list submissions to
> open-ils-general at list.georgialibraries.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://libmail.georgialibraries.org/mailman/listinfo/open-ils-general
> or, via email, send a message with subject or body 'help' to
> open-ils-general-request at list.georgialibraries.org
>
> You can reach the person managing the list at
> open-ils-general-owner at list.georgialibraries.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Open-ils-general digest..."
>
>
> Today's Topics:
>
> 1. Re: Problem installing opensrf 1.2.3 on Karmic (Dan Scott)
> 2. Re: Serials in alpha4 (Repke de Vries)
> 3. Re: 852 broken in 1.6 Staff Client Batch Import too ? Stuck
> with 2.0 alpha4 Staff Client importing 852 Item Information
> (Repke de Vries)
> 4. Re: Evergreen 2.0 beta 1, testing standards-based control
> numbers (Bill Erickson)
> 5. Re: Serials in alpha4 (Kathy Lussier)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 7 Nov 2010 12:23:13 -0500
> From: Dan Scott <dan at coffeecode.net>
> Subject: Re: [OPEN-ILS-GENERAL] Problem installing opensrf 1.2.3 on
> Karmic
> To: Evergreen Discussion Group
> <open-ils-general at list.georgialibraries.org>
> Message-ID: <20101107172313.GA7028 at dbs.denials>
> Content-Type: text/plain; charset=us-ascii
>
> On Sun, Nov 07, 2010 at 09:24:54AM +0200, chigwagwap at msu.ac.zw wrote:
>>
>> Dear All
>>
>> i m trying to install opensrf 1.2.3 on kamic and i m getting an
>> error message
>>
>> RPC failed on the node ejabberd at libserver: {'EXIT',
>> {badarg,
>> [{erlang,port_control,
>> [stringprep_port,1,
>> "private.localhost"]},
>> {stringprep,control,2},
>> {jlib,nameprep,1},
>>
>> {ejabberd_auth,auth_modules,1},
>> {ejabberd_auth,is_user_exists,2},
>>
>> {ejabberd_auth,try_register,3},
>> {ejabberd_ctl,process,1},
>> {rpc,'-handle_call/3-fun-0-',
>> 5}]}}
>> upon trying to register router and opensrf users.
>> What am i suppposed to do
>>
>
> The error message makes it sound like there might be a configuration
> error in your ejabberd.cfg file in the 'hosts' clause. Could you copy
> and paste that section of your ejabberd.cfg file into a reply? Are you
> able to stop and start ejabberd?
>
> I should also note that there's not much reason to install OpenSRF 1.2.3
> anymore, unless you're just upgrading an existing system. OpenSRF 1.6.x
> is even the recommended version for Evergreen 1.6 now (I'm about to
> update the downloads page accordingly).
>
>
> ------------------------------
>
> Message: 2
> Date: Sun, 7 Nov 2010 21:16:09 +0100
> From: Repke de Vries <repke at xs4all.nl>
> Subject: Re: [OPEN-ILS-GENERAL] Serials in alpha4
> To: Evergreen Discussion Group
> <open-ils-general at list.georgialibraries.org>
> Message-ID: <18D672BB-F6B1-443B-87BA-4E82FB92F756 at xs4all.nl>
> Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
>
> Exactly the scenario at IISH Tim, at least for part of our serials
> collection.
>
> And Dan Scott is all too right for both of us:
> "..
>>> looking for a way to populate the new
>>> serials tables with legacy MFHD data. And I'm not sure there
>>> currently
>>> is a way to get there from here, where "here" =
>>> serial.record_entry or
>>> your previous ILS's export of MFHD records.
> .."
>
> And I am not a (PostgreSQL) database expert but it seems attractive
> to create "some sort of in-database solution that parses the rows of
> MFHD Holding Record information in serial.record_entry and uses that
> to populate those new serials tables" and that way build on the
> already existing marcbre + marcsre tools rather than create an
> external tool from scratch - probably based on a "staging table"
> approach?
>
> I would also like to point out and stress the following:
>
> also an EXPORTING command line tool for these new serials tables is
> missing: this would rebuild a full MFHD record from those tables.
> That way you can:
> - be sure that the new Serials Management functionalities "do the
> right thing" :-) with your MFHD (legacy) data
> - avoid "data lock-in" : if at some point you wish to move from the
> "Evergreen ILS" to " Futuregreen" you can be sure of MARC compliant
> MFHD to do so
>
> Repke
>
> Op 6-nov-2010, om 23:04 heeft Tim Spindler het volgende geschreven:
>
>> Specifically we are looking at exporting Marc with 853, 863 , etc and
>> importing into Evergreen. If I understand serials module correctly, it
>> builds prediction schedule from mtgs publication pattern.
>>
>> Sent from my iPhone
>>
>> On Nov 6, 2010, at 2:02 AM, Dan Scott <dan at coffeecode.net> wrote:
>>
>>> On Fri, Nov 05, 2010 at 03:36:06PM -0400, Mike Rylander wrote:
>>>> On Fri, Nov 5, 2010 at 2:15 PM, Tim Spindler
>>>> <tjspindler at gmail.com> wrote:
>>>>> Regarding the command line and the MFHD, will/does Vandelay support
>>>>> importing the MFHD fields???? We are hoping this will be our
>>>>> path to migrating
>>>>> serials data when we go live.
>>>>>
>>>>
>>>> There is, indeed, such a command line tool. The indomitable Dan
>>>> Scott
>>>> added Open-ILS/src/extras/import/marc2sre.pl a while back for the
>>>> purpose of priming MFHD records. It requires that you have the
>>>> internal ID of your Evergreen bib records embedded in the MFHD
>>>> records
>>>> that link to said. Beyond that restriction, you simply point it at
>>>> your MFHD MARC and it will generate a file full of 'sre' records
>>>> suitable for loading with pg_loader, just like 'bre' and 'are'
>>>> records.
>>>
>>> Aw, that's nice of you Mike, but I think the question was more
>>> about the
>>> new serials support (check-in UIs and circulating serials) and less
>>> about the non-circulating serials MFHD-based support. If I read
>>> Tim and
>>> Repke's questions right, they're looking for a way to populate the
>>> new
>>> serials tables with legacy MFHD data. And I'm not sure there
>>> currently
>>> is a way to get there from here, where "here" =
>>> serial.record_entry or
>>> your previous ILS's export of MFHD records.
>>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Sun, 7 Nov 2010 22:25:47 +0100
> From: Repke de Vries <repke at xs4all.nl>
> Subject: Re: [OPEN-ILS-GENERAL] 852 broken in 1.6 Staff Client Batch
> Import too ? Stuck with 2.0 alpha4 Staff Client importing 852 Item
> Information
> To: Evergreen Discussion Group
> <open-ils-general at list.georgialibraries.org>
> Message-ID: <37E8E1BF-BA61-4926-86DD-4BE8290ED759 at xs4all.nl>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>
> Any help appreciated!
>
> Did additional testing in 1.6.0.1 and what used to work for us in
> that version a number of months back , doesn't anymore.
>
> Here is an an example [1]: BroGroepCanadaBR1Combi.mrc in http://
> www.xs4all.nl/~repke/Evergreen/
> adopted for out-of-the-box Evergreen
>
> And these are the steps in the Staff Client:
> 1) Cataloging -> MARC Batch Import/Export
> 2) create an upload queue; mark "auto import non-colliding records',
> mark "import attached holdings"; choose "file to upload"
> 3) click Upload: the record gets imported
> 4) search the catalog for the record
>
> Copy information should be shown now for BR1 but it doesn't anymore
> in 1.6.0.1 and neither does it in 2.0 alpha4. The latter could be
> caused by additional MARC Batch Importer / Exporter settings that we
> maybe don't understand yet (see below).
>
> Can anyone reproduce the situation or in anyway help with the right
> additional settings in 2.0 for MARC Batch Importer / Exporter?
>
> Especially for quick tests, the Importer is very convenient.
>
> Thanks a lot, Repke, IISH
>
> [1]
> =LDR 00569npm 2200181 45 0
> =001 IISGb11016444
> =003 IISG
> =005 20081119170854.0
> =008 070221s\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
> =040 \\$aNe$dAmISG
> =041 0\$akh
> =044 \\$aeng
> =245 10$aDemocratic Kampuchea / Kampuchea Democratique : collection
> of brochures$f1975-1978
> =300 \\$a0.1 m
> =500 \\$aGroepsbeschrijving
> =520 8\$aA collection of 33 brochures and 4 illustrated magazines
> from Democratic Kampuchea (1975-1978)
> =605 \0$aSEA$eCambodia
> =852 00$aIISG$bBR1$bBR1$hBro 2541 fol$pN10745146
>
>
> Op 5-nov-2010, om 17:42 heeft Repke de Vries het volgende geschreven:
>
>> Hi all
>>
>> trying to MARC Batch Import / Export import a single record +
>> attached holding [3] that used to import fine in EG 1.6
>>
>> and stuck: the 852 item information keeps being ignored:
>> - because we changed the Org Units Structure [2] I went back to a
>> fresh alpha4 Virtual Image and tried the usual 852 $bBR1 etc.: no
>> result
>> - given the changed Org Units Structure I tried an import with
>> $bBR2 'cause that branch still hangs around: no result
>> - blush: a few hours I learned from this list (Dan Scott answers)
>> that in 2.0 we now have an Edit Import Item Attributes: very
>> welcome tool, noticed the attribute "Keep" being False and made
>> that True (see [1] for the Item Attributes), started new staff
>> client session: still no result
>>
>> I now have the feeling I miss some finer point in 2.0 that wasn't
>> there in the more blunt 1.6: any pointers ?
>> Maybe changing Item Attributes in the Staff Client needs an
>> additional command line Autogen or xx to complete?
>>
>> Stuck !!
>>
>> Thanks, Repke
>>
>> [1] the attributes in the Edit Import Item Attributes screen:
>> Part 1: http://screencast.com/t/vrkLGsiCZ
>> Part 2: http://screencast.com/t/S7lFazlwx6e
>>
>> [2] our Org Units Structure: http://screencast.com/t/lByuAYLlbAIK
>> and the (lowest) IISG level can have Items and Copies
>> [3] we always import in ".mrc" but for mortals the record looks
>> like this and with BR1 instead of IISG imported fine in EG 1.4 and
>> 1.6:
>>
>> =LDR 00734nav 2200217 a 45 0
>> =001 IISGb10923000
>> =003 IISG
>> =005 20040426114843.0
>> =008 040426s\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
>> =040 \\$aNe$dAmISG
>> =245 10$kBeelddocument = Visual document$f1985-1992
>> =603 \0$aAffiche$bPoster
>> =604 \0$aXX-4
>> =605 \0$aCAN$eCanada
>> =710 0\$aPublic Service Alliance of Candada
>> =852 00$bIISG$bIISG$cNEHA$hBG D32/958$p30051001607255
>> =852 00$aIISG$bIISG$bIISG$hBG D32/959$p30051001607644
>> =852 00$aIISG$bIISG$bIISG$hBG D32/960$p30051001607594
>> =852 00$aIISG$bIISG$bIISG$hBG D32/961$p30051001607545
>> =852 00$aIISG$bIISG$bIISG$hBG D32/962$p30051001607495
>> =852 00$aIISG$bIISG$bIISG$hBG D32/963$p30051001607446
>
>
>
> ------------------------------
>
> Message: 4
> Date: Mon, 8 Nov 2010 08:59:24 -0500
> From: Bill Erickson <erickson at esilibrary.com>
> Subject: Re: [OPEN-ILS-GENERAL] Evergreen 2.0 beta 1, testing
> standards-based control numbers
> To: Evergreen Discussion Group
> <open-ils-general at list.georgialibraries.org>
> Message-ID:
> <AANLkTimfkY-k6uVBE-wwti2ttD=LzL5oJZymj2DA=nDh at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> On Sat, Nov 6, 2010 at 2:28 AM, Dan Scott <dan at coffeecode.net> wrote:
>
>> Hey all:
>>
>> Mike Rylander finished wrapping up the 2.0 beta 1 release at
>> http://evergreen-ils.org/downloads/Evergreen-ILS-2.0-beta1.tar.gz (the
>> downloads page / wiki install instructions still need to be updated, so
>> this is a bonus heads up for mailing list readers).
>>
>> If possible, I'd like people to give things a test after explicitly
>> turning on two global flags that have been in place, but turned off,
>> since the first 2.0 release. If you haven't found them yet in your
>> explorations, "Global Flags" are located under "Admin -> Server Settings
>> -> Global Flags" in the staff client, and they're used to affect the
>> behaviour of the Evergreen system globally. (Maybe we should rename it
>> to "Global Behavior" to avoid any chance that people might think they're
>> opening up a screen with flags of the world?)
>>
>> The settings in question are:
>>
>> * "Cat: Use internal ID for TCN value" - this uses the record ID (you
>> could call it the accession number) of the record for the title control
>> number (TCN).
>>
>
> There's one caveat to enabling this setting. Using the internal identifier
> as the TCN effectively disables the collision detection in the Z39.50 import
> interface, since it's based on TCN value. (The TCN-based collision
> detection is so rudimentary, though, some may be relieved by this). Until a
> more flexible collision detection process is in place, avoiding duplicate
> bib record imports from Z39.50 will be up to the user.
>
> Thanks for the nudge, Dan.
>
> -b
>
> --
> Bill Erickson
> | VP, Software Development & Integration
> | Equinox Software, Inc. / Your Library's Guide to Open Source
> | phone: 877-OPEN-ILS (673-6457)
> | email: erickson at esilibrary.com
> | web: http://esilibrary.com
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://libmail.georgialibraries.org/pipermail/open-ils-general/attachments/20101108/97b920e8/attachment-0001.htm
>
> ------------------------------
>
> Message: 5
> Date: Mon, 8 Nov 2010 09:41:24 -0500
> From: "Kathy Lussier" <klussier at masslnc.org>
> Subject: Re: [OPEN-ILS-GENERAL] Serials in alpha4
> To: "'Evergreen Discussion Group'"
> <open-ils-general at list.georgialibraries.org>
> Message-ID: <920462CC31D34DB0A8F9B2F99ACCFEC9 at CWCENTRAL.internal>
> Content-Type: text/plain; charset="US-ASCII"
>
> Thank you Lebbeous and Dan!
>
> Lebbeous, I did indeed have more success with the alternate serials view. I
> also like the wizards for creating publication patterns and issuances. I ran
> across a little trouble generating the predictions, but there are a couple
> of things I want to check on our end later this week to see if I can get it
> going.
>
> Dan, thanks for taking a look into it! We had come across some of these
> problems earlier in our testing, but, since we are still new to Evergreen,
> it's difficult to know what is caused by a problem in our own setup and what
> is a bug. I look forward to hearing what you find!
>
> Kathy
>
>
>
> -------------------------------------------------------------
> Kathy Lussier
> Project Coordinator
> Massachusetts Library Network Cooperative
> (508) 756-0172
> (508) 755-3721 (fax)
> klussier at masslnc.org
> IM: kmlussier (AOL & Yahoo)
> Twitter: http://www.twitter.com/kmlussier
>
>
>
>
>> -----Original Message-----
>> From: open-ils-general-bounces at list.georgialibraries.org
>> [mailto:open-ils-general-bounces at list.georgialibraries.org]
>> On Behalf Of Dan Wells
>> Sent: Friday, November 05, 2010 8:49 PM
>> To: open-ils-general at list.georgialibraries.org
>> Subject: Re: [OPEN-ILS-GENERAL] Serials in alpha4
>>
>> Hello Kathy,
>>
>> Thank you very much for this report. I am probably wrong, but
>> I think this might be the first report from anyone using
>> these interfaces outside of myself and the folks at Equinox,
>> and it is something I have really been hoping for. It is so
>> easy when testing one's own code to make many assumptions,
>> and some errors, once avoided, never resurface.
>>
>> This probably boils down to some small oversight on my part,
>> but I'll get to the bottom of it first thing Monday and let
>> you know what I find.
>>
>> Sincerely,
>> Dan
>>
>> **************************************************************
>> *******************
>> Daniel Wells, Library Programmer Analyst dbw2 at calvin.edu
>> Hekman Library at Calvin College
>> 616.526.7133
>> >>> "Kathy Lussier" 11/05/10 11:18 AM >>>
>> Hi all,
>>
>> I've been digging into serials on a 2.0 alpha4 installation
>> by following the
>> notes at
>> http://open-ils.org/dokuwiki/doku.php?id=acq:serials:release_n
> otes:initial_t
>> runk_merge, but I've run into various stumbling blocks and
>> can't get to the
>> point where I can successfully receive an issue. I'm not sure
>> if I'm doing
>> things incorrectly, if the problems I've run across are for
>> areas that are
>> still being worked on, or if they are bugs I should be submitting.
>>
>> I have created templates using the copy templates editor, but
>> when I create
>> a distribution, this template is not populating the template
>> dropdown menus.
>> After I save the distribution, I can go into the database to
>> associate the
>> distrubtion with my template, but I'm wondering if anyone has
>> had success
>> identifying the template in the UI. Also, nothing appears in
>> the dropdown
>> menus for call numbers, and I'm not sure how to add one.
>>
>> Once I create the distribution, I can successfully create a
>> caption/pattern
>> and the first issuance using the sample pattern codes and
>> holdings code
>> provided in the notes. When I make predictions for the
>> subscription, I
>> receive a message similar to the one in the attached image on
>> each item for
>> which I am creating a prediction. However, despite these
>> popup boxes, the
>> system does create the issuances after completing this process.
>>
>> I then head over to the items tab for the record, click on
>> one of the items,
>> and then click the receive button to try to receive an issue.
>> The system
>> returns an error message and is unable to receive the item. I
>> suspect some
>> of the problems I came across earlier in the process may be
>> responsible for
>> the fact that I can't receive an issue. Has anyone
>> successfully received an
>> item in serials?
>>
>> Thanks in advance for any help you can provide!
>>
>> Kathy Lussier
>>
>> -------------------------------------------------------------
>> Kathy Lussier
>> Project Coordinator
>> Massachusetts Library Network Cooperative
>> (508) 756-0172
>> (508) 755-3721 (fax)
>> klussier at masslnc.org
>> IM: kmlussier (AOL & Yahoo)
>> Twitter: http://www.twitter.com/kmlussier
>>
>
>
>
> End of Open-ils-general Digest, Vol 53, Issue 13
> ************************************************
>
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
More information about the Open-ils-general
mailing list