ESciDoc Search Index Publication metadata context

Publication metadata context

This page specifies indexing requirements for derived indexes (compound&any) for the Publication metadata context.

• see general rules at eSciDoc Search Index Names

Creator indexes

See also PubMan_Indexing#Persons_.28escidoc.any-persons.29
Stated: Creator.Person.CompleteName with Creator.CreatorType = "Person"

• Automatically generated indexes are:

       publication.creator.person.{complete-name, family-name, given-name, identifier}
       publication.creator.person.organization.{organization-name, address, idenfier}
       publication.source.creator.person.{complete-name, family-name, given-name, identifier}
       publication.source.creator.person.organization.{organization-name, address, idenfier}
       publication.creator.organization.{organization-name, address, identifier}

• Compound&Any indexes
  • Note: for all complete-name like compound/any indexes, please check Complete name indexing tokons

       1) publication.creator.person.compound.person-complete-name 

1) Derived from the metadata publication.creator.person.family-name, publication.creator.person.given-name, sortkey field values sorted previously by order of entry i.e. position in the xml

       2) publication.source.any.person-complete-name 

2) Derived from the metadata publication.source.creator.person.family-name, publication.source.creator.person.given-name, and any sub-sources that would exist, sortkey field values sorted previously by level (i.e. publication, source1, source1.2, source 1.3, source 2, source 2.1, source 2.2) and order of entry i.e. position in the xml

       3) publication.creator.compound.organization-path-identifiers 

3) Derived from identifiers of the organizational unit referenced in the metadata (at publication creator level i.e. creator.organization, creator.person.organization) and all parents of that organizational unit, see Organization index examples

       4) publication.creator.any.organization-path-identifiers 

4) Derived from identifiers of the organizational unit referenced in the metadata (at any creator level i.e. creator.organization, creator.person.organization, source.creator.organization, source.creator.person.organization, source.source.creator.person.organization, source.source.creator.organization etc.) and all parents of that organizational unit

       5) publication.compound.publication-creator-names

5)Derived from all creator names such as: publication.creator.person.family-name, publication.creator.person.given-name, publication.creator.organization.organization-name, sortkey field values sorted previously by order of entry i.e. position in the xml

       6) publication.any.publication-creator-names

6)Derived from all creator names at any level of publication or source (including embedded sources) such as: publication.creator.person.family-name, publication.creator.person.given-name, publication.creator.organization.organization-name, publication.creator.organization.organization-name, publication.source.creator.person.family-name, publication.creator.person.given-name, publication.source.creator.organization.organization-name, publication.source.creator.organization.organization-name, etc., sortkey field values sorted previously by level (i.e. publication, source1, source1.2, source 1.3, source 2, source 2.1, source 2.2) and order of entry i.e. position in the xml

Title indexes

• Automatically generated indexes

           publication.title
           publication.alternative
           publication.source.title
           publication.source.alternative
           publication.event.title
           publication.event.alternative
           publication.source.source.title
           publication.source.source.alternative
           ...
           

• Compound&Any indexes

        1) publication.compound.titles

1) Derived from publication.title, publication.alternative, sortkey field values as specified order of derivation

        2) publication.compound.topic

2) Derived from publication.title, publication.alternative, publication.tableOfContents, publication.abstract, publication.subject, sortkey filed values as specified order of derivation

        3) publication.event.compound.title-place

3) Derived from publication.event.title, publication.event.alternative, publication.event.place, sortkey field values as specified order of derivation

        4) publication.source.any.title

4) Derived from publication.source.title, publication.source.alternative, and any embedded sources, sortkey field values as positioned in the xml (i.e. source1, source1.1, source1.2, source2 etc.)

Date indexes

• Compound&Any indexes

     1) publication.compound.dates

1) Derived from publication.created, publication.modified, publication.dateSubmitted, publication.dateAccepted, publication.published-online, publication.issued, sortkey field should be populated with logic specified at PubMan Sorting (Default system sorting)

     2) publication.compound.most-recent-date

2) Derived as most recent date from any value if exists in following date metadata:

  publication.created, publication.modified, publication.dateSubmitted, publication.dateAccepted, publication.issued, publication.published-online

Sort logic is specified as sorting by most-recent-date from any value if exists in following order:

  publication.created, publication.modified, publication.dateSubmitted, publication.dateAccepted, publication.issued,  properties.last-revision, properties.created

Identifier indexes

• Compound&Any indexes

     1) publication.any.identifier

1) Derived from publication.identifier, publication.source.identifier, publication.source.source.identifier (and any further embedded sources), See also Special requirements and remarks on normalization