project-cdsware-users@cern.ch archives


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

*SPAM* Re: submission/search problems on demo site


  • From: "Stuart L. Marshall" <marshall@xxxxxxxxxxxxxxxxx>
  • Subject: *SPAM* Re: submission/search problems on demo site
  • Date: Fri, 22 Jul 2005 07:29:11 -0700

Hi,

> What collection does the record belong to?  What's the value of the
> collection indicator tag (980) that you see in
>
>    http://xxx.stanford.edu/cds/search.py?recid=153&of=hm
>
> Does it correspond to the definition of the collection you want it to
> appear in?
>
> (E.g. published articles demo records have 980 tag equal to
> ``ARTICLE'', and the collection definition reads
> ``collection:ARTICLE''.)
>
> Moreover, does this collection belong to the public collection tree
> associated somewhere under the Home collection, as its regular
> descendant?
>

It is "000000153 980__ $$aPICTURE"

This is the result of submitting using the submit menu item,
choosing the picture document type and then "diagrams and charts".
I would assume this goes in the top level collection?

Record #83 which came with the demo set up shows the same
value "000000083 980__ $$aPICTURE".

Thanks for the php info, I may have only done the php mods in the
apache version of the file (debian set up).

Quoting Tibor Simko (tibor.simko@xxxxxxx) on Fri, Jul 22, 2005 at 09:53:49AM +0200:
> Hello
>
> On Thu, 21 Jul 2005, Stuart L. Marshall wrote:
> > (I forgot, I think I needed to change the second line of
> > the bibupload php script from:
> >    <?
> >    to
> >    <?php
>
> Please note that the INSTALL file recommends to put this into your
> php.ini:
>
>    log_errors = on
>    display_errors = off
>    expose_php = off
>    max_execution_time = 160
>    register_globals = on
>    short_open_tag = on
>
> If the ``short_open_tag'' directive is on, then you don't have to use
> ``<?php''.  All our PHP scripts assume it's on.
>
> > So some additional step is needed to make the record # 153 visible.
>
 
> > so I am running webcoll every 10 minutes and the others every hour.
>
> That's not really necessary.  Webcoll doesn't see new records unless
> indexes are up to date.  (At least the ``collection'' index.)  Hence
> if bibindex runs at 10:00 and you integrate a new record at 10:01, it
> will be indexed by the next bibindex run at 11:00 and the webcoll will
> see it only after the 11 o'clock job finishes.
>
> If you want to integrate new records fast, then you better diminish
> the frequency to 10 minutes for all the tasks.
>
> If you want to integrate new records fast without waiting for delays
> associated to the output formatting and other author/title indexing
> jobs, then you can try to run a setup like this:
>
>    $ bibindex -wcollection -s10m
>    $ webcoll -s10m -v0
>    $ bibindex -s1h
>    $ bibreformat -oHB,HD -s1h
>    $ bibrank -s1h
>
> Tibor

--
- Stuart Marshall       650 926 3616                Office
- KIPAC/SLAC M/S 29         926 4310                Dept Office
- 2575 Sand Hill Rd.        926 8570                FAX
- Menlo Park, CA 94025  marshall@xxxxxxxxxxxxxxxxx  E-mail