Re: How does 773 field work? How to represent journals?

[Ferran Jorba <Ferran.Jorba@xxxxxx>]

Hi Tibor,

Sorry for not answering before. I'm working on it as time permits.

[...]
> CDSware comes preconfigured for 909C4.  If your publication
> information is stored elsewhere, like in 773, you should reconfigure
> the output display in the BibFormat Admin.  Namely, choose menu
> ``Extraction Rules'' to add tag 773 and its subfields, then choose

Ok, that's what I've done, and I'm explaining it so maybe somebody
else can learn with me:

    Add new Extraction Rule

                 Type [              ]
        Variable name [              ]
           Field Type [ datafield |v|]
  Attribute TAG value [              ]
 Attribute IND1 value [              ]
 (only for datafield)
 Attribute IND2 value [              ]
 (only for datafield)

After playing with tye Type field, writing in some random value,
it creates a new table to the big "DEFAULT" one.  So I removed
my extraction rule and typed in DEFAULT instead.

For variable name, after reading the guide, and not being able
to find how to name it, finally I learned that a number can
perfectly be a variable name.  So I called 773 to my variable.
I left field type to 'datafield', and the two indicators empty.

Then the DEFAULT table was updated, with my new 773 varname. Good:

 773 <datafield tag="773" ind1="" ind2=""> Yes [Modify] [Add Subfield] [Delete]

Then I had some trouble with popups, as I ban them with Mozilla.
So I gave permisions to my site.  This popup reads:

 Extraction Rules

 Add new subfield to variable'DEFAULT - 773'
 Subfield name:           [            ]
 Attribute "label" value: [            ]
           [Submit Query]

After trying some values and watching the table being updated, I
concluded that the both fields can be something as simple as the
subfield "letter".  So I typed 'p' and 'p'.  However, in my
updated table, the "SF Name" (Subfield Name) appears in uppercase,
while the rest of the tags have SF names in lowercase. As much
as I've tried, I haven't been able to fix it.  Is this a bugglet?

> menu ``Formats'' to modify format ``_FULL_PUBLIINFO'' and friends by
> displaying 773 instead of 909C4 there.  Then force bibreformat for the

Is it legal to add another "if" to the current one?  So, if in this
form there is already a

 if($909C4.p!=""){
  "<br><br><strong>Published in: </strong>"
  ...
  ...

I've added another one like

 if($773!=""){
  "<br><br><strong>Published in: </strong>"
  if ($773.P!="") {
     REP($773.P," ","+")
     $773.P " "
     $773.Y
   }
 }

(I've had to resort to a copy&paste to emacs to balance the brakets,
because it was complaining about them, how nice!)
Or should I have a single "if"?  As I have a readonly knowledge of
PHP syntax, I was unsure about the "else if" syntax.

> HD behaviour (HD=HTML Detailed) for all your records that have 773,
> and you should be done.

I went to bibsched and choose the manual mode to run my already
submitted 'bibreformat -oHB,HD -s5m' (yes, I know it runs very often,
but then, I need to know results quite often).

But my records don't seem to be reformatted. What I am missing?

Thanks,

Ferran