To play the role of NHSE librarian, the steps are as follows:

To process a new submission:

1.  After you have received email from the CGI nhse-submit-software
script (alias nobody) and the PGP-signed urc file from the contributor,
go to /netlib/nhse/software/submissions.  Save the PGP-signed urc
file, minus the mail header, with a .asc extension.

2.  Decrypt the signed urc file (do pgp -h to find out how)
and compare with the urc file put there by the script.  They
should be the same.  Keep the .asc file around because it is
a record of the authentication.
(PGP is currently installed on the cs machines, but not on netlib2
that I can tell.  Do you want me to ask about installing PGP on netlib2,
or do you just want to do the PGP stuff on your cs account -- the
latter is where I receive nhse-librarian mail anyway, since I
have .forward on netlib2 set to browne@cs.utk.edu).

3.  Add <category> and <keywords> fields to the urc file.
Category should be one of the following:
  application     (application libraries and programs)
  benchmark      (benchmark and example programs)
  data-analysis-vis   (data analysis and visualization tools)
  numerical  (numerical libraries and routines, including computational
            geometry)
  ppt-comm (parallel processing tools/communication libraries)
  ppt-exe  (parallel processing tools/execution and performance analyzers,
            including debuggers)
  ppt-env  (parallel processing tools/parallel programming environments)
  ppt-io   (parallel I/O systems)
  ppt-pplang (parallel processing tools/parallel programming languages
            and compilers)
  ppt-pplib (parallel processing tools/parallel programming libraries)
  ppt-rts  (parallel processing tools/runtime systems)
  ppt-scr (parallel processing tools/source code analyzers and restructurers)
  ppt-misc   (parallel processing tools/miscellaneous)
If you assign more than one category, all will be
used in generating the table of contents lists for the software catalog.
Keywords should be chosen from the HPCC thesaurus, only adding new
keywords if no existing keywords are suitable.

4.  If they asked for partial review, do it.
    (Create a file with a record of the partial review, call it
     <top-md5>.partial-review.<format> ?)

5.  Move files from submissions subdirectory to processed subdirectory.
    (can use /usr/local/netlib/bin/nhse/nhse-lifn-move for this, although
    it doesn't currently move the .asc or .partial-review. files)

6.  Add submission to software catalog.


To process a change request:

Same as above except change submission will be in changes subdirectory.


Questions/Changes:

1.  Should we create a separate subdirectory for each contribution?

2.  Should we keep superceded submissions in processed or move
    to a different directory -- e.g., old?

3.  Should we save old urc file when cataloging information changes
    but top-level md5, and thus the lifn, doesn't?


To do list:
1.  Automatic generation of software catalog.

2.  Write form and CGI script to display the URC for a LIFN.
    This will be used from the software catalog or directly
    by a user.


Shirley