This is an automated notification sent by LCG Savannah.
It relates to:
                task #7572, project CDS Invenio

==============================================================================
 LATEST MODIFICATIONS of task #7572:
==============================================================================

Update of task #7572 (project cdsware):

             Assigned to:                    None => skaplun                


==============================================================================
 OVERVIEW of task #7572:
==============================================================================

URL:
  <http://savannah.cern.ch/task/?7572>

                 Summary: Derived Logical Fields (or Meta Fields)
                 Project: CDS Invenio
            Submitted by: skaplun
            Submitted on: 2008-08-11 16:53
         Should Start On: 2008-08-11 00:00
   Should be Finished on: 2008-08-11 00:00
                Category: WebSearch
                Priority: 5 - Normal
                  Status: None
                 Privacy: Public
        Percent Complete: 0%
             Assigned to: skaplun
             Open/Closed: Open
         Discussion Lock: Any
                  Effort: 0.00

    _______________________________________________________


It would be nice to extend logical fields to support generic functions that
given the MARC of a record returns a list of strings.

These logical derived fields would be available at indexing time, searching
time and formatting time (e.g. via a bfe_derived_logical_field). 

They could be based on a plugin structure (as in BibFormat), with a
well-defined API. E.g. the function could accept the record object, and
return a list of tuple (derived string, relative MARC field if appropriate or
None otherwise, if the relative MARC field exists the string could be thought
as a subfield).

E.g. suppose that you have 123__ $a  SURNAME $b  NAME. Then a function can
take the above MARC and return:

[("SURNAME, N.", 123__ $a  SURNAME $b  NAME), ...]

BibIndex/WebSearch can just care about the string part, while BibFormat could
exploit also the knowledge about the relative field (if appropriate), to
create e.g. sensible HTML links with smart text.





    _______________________________________________________

Carbon-Copy List:

CC Address                          | Comment
------------------------------------+-----------------------------
2195                                | -SUB-




==============================================================================

This item URL is:
  <http://savannah.cern.ch/task/?7572>

_______________________________________________
  Message sent via/by LCG Savannah
  http://savannah.cern.ch/


Reply via email to