Skip to main content
Support - EBSCO Help

What are the fields available for uploading my holdings to Full Text Finder?

You can enter column headers manually or download a Microsoft® (MS) Excel spreadsheet template with all the column headers already entered. The column headers are not case-sensitive.

You can use MS Excel to modify the list, but save the file as a tab-delimited text (.txt) file before you upload it. Be sure to save as a Unicode text (.txt) file when using world languages that upload in Unicode.

Following is a list of column headers and their acceptable values:

KBID
  • Acceptable Value(s):
    • Integer
  • A unique number that EBSCO creates and assigns to a title.

Title
  • Acceptable Value(s):
    • Text
    • Null (If package upload only or not creating a custom resource)
  • Resource or title name. (This column accepts Unicode.)
  • Required for custom titles. Y  in the IsCustom column of a downloaded file indicates a custom title.

AlternateTitle
  • Acceptable Value(s):
    • Text
    • Null
  • Used for Matching Resources, for example:
    • Sound of Music
    • Sound of Music 25th anniversary
    • Sound of Music:video recording

PackageName
  • Acceptable Value(s):
    • Text - 200 character maximum
  • The name of the package or database this title is included in.
  • On Publication Finder, the Source displays as a link (pointing to the URL entered in the URL column) under the title name.
  • If you do not want the Source to be a link, do not enter any information in the URL column.
  • Required for custom titles. Y  in the IsCustom column of a downloaded file indicates a custom title.

URL
  • Acceptable Value(s):
    • Null
    • URL - 700 character maximum
  • On Publication Finder, the hyperlinked source will link to the URL included in this column.
  • For trial accounts, URLs for managed titles are omitted from the download list.

Publisher
  • Acceptable Value(s):
    • Null
    • Text - 700-character maximum
  • Use this field in your upload to add or update a Custom Resource's Publisher.

Edition
  • Acceptable Value(s):
    • Null
    • Text
  • Use this field in your upload to add or update a Custom Resource's Edition.

Author
  • Acceptable Value(s):
    • Null
    • Text
  • Use this field in your upload to add or update a Custom Resource's Author(s)

Editor
  • Acceptable Value(s):
    • Null
    • Text
  • Use this field in your upload to add or update a Custom Resource's Editor(s)

Illustrator
  • Acceptable Value(s):
    • Null
    • Text
  • Use this field in your upload to add or update a Custom Resource's Illustrator(s)

PrintISSN
  • Acceptable Value(s)::
    • Null
    • Text 
  • EBSCO automatically enters and updates this column for managed resources and these values can not be overridden.
  • For custom resources, any format can be used in an upload file as long as character limit is not exceeded.

OnlineISSN
  • Acceptable Value(s):
    • Null
    • Text
  • EBSCO automatically enters and updates this column for managed resources and these values can not be overridden.
  • For custom resources, any format can be used in an upload file as long as character limit is not exceeded.

PrintISBN
  • Acceptable Value(s):
    • Null
    • Text
  • EBSCO automatically enters and updates this column for managed resources and these values can not be overridden.
  • For custom resources, any format can be used in an upload file as long as character limit is not exceeded.

OnlineISBN
  • Acceptable Value(s)::
    • Null
    • Text
  • EBSCO automatically enters and updates this column for managed resources and these values can not be overridden.
  • For custom resources, any format can be used in an upload file as long as character limit is not exceeded..

DOI
  • Acceptable Value(s):
    • Null
    • Text
  • Managed Resource - Cannot override EBSCO entered value.
  • Custom Resource - Supports any format you enter in your upload file as long as character limit is not exceeded.

PeerReviewed
  • Acceptable Value(s):
    • Y
    • N
    • Null
  • Not case sensitive
  • If an EBSCO Managed Resource the value is ignored
  • If a Custom Resource the value is supported
  • "Y" = classifies a title as Peer Reviewed
  • "N" = classifies a title as not Peer Reviewed
  • No value entered = classifies a title as not Peer-Reviewed
  • If column is not present then the title is classified as not Peer-Reviewed

CustomCoverageBegin
  • Acceptable Value(s):
    • yyyy-mm-dd, yyyy/mm/dd, yyyy.mm.dd
    • mm/yyyy, mm yyyy, yyyy
    • Null
    • No Access
    • to present, -present, present
  • A 100-character free-form field.
  • Information for the beginning of the resource's coverage based on your institution's subscriptions, maintained by your institution's administrator. 
  • Enter custom coverage for titles with coverage different than the default coverage or for titles with coverage not managed by EBSCO.
  • Can apply to managed or custom titles. (This column accepts Unicode.)
  • If utilizing the A-to-Z link feature within EBSCOadmin, any dates entered within the CustomCoverage fields will apply to the Local Collection that populates into EBSCOadmin.
    Note: If you are using Microsoft Excel to enter custom coverage by upload, please ensure that Excel does not automatically format the dates to a type that is unreadable by EBSCO. Otherwise, your custom coverage will not be added.

CustomCoverageEnd
  • Acceptable Value(s):
    • yyyy-mm-dd, yyyy/mm/dd, yyyy.mm.dd
    • mm/yyyy, mm yyyy, yyyy
    • Null
    • No Access
    • to present, -present, present
  • A 100-character free-form field.
  • Information for the end of the resource's coverage based on your institution's subscriptions, maintained by your institution's administrator. 
  • Enter custom coverage for titles with coverage different than the default coverage or for titles with coverage not managed by EBSCO.
  • Can apply to managed or custom titles. (This column accepts Unicode.)
  • Leaving this field blank, causes to present to display on Publication Finder.
  • If utilizing the A-to-Z link feature within EBSCOadmin, any dates entered within the CustomCoverage fields will apply to the Local Collection that populates into EBSCOadmin.
    Note: If you are using Microsoft Excel to enter custom coverage by upload, please ensure that Excel does not automatically format the dates to a type that is unreadable by EBSCO. Otherwise, your custom coverage will not be added.

CoverageStatement
  • Acceptable Value(s):
    • Null
    • Text
  • Use this field in your upload to specify coverage for Managed and Custom resources in dates and text.
  • Overrides all selected resource coverage statement values

CustomEmbargo
  • Acceptable Value(s):
    • Null
    • Postiive Integer (greater than 0 + a single unit of time (days, weeks, months, years)
  • Use this field in your upload when uploading custom titles to enter embargo information.

Description
  • Acceptable Value(s):
    • Null
    • Text
  • Use this field in your upload to add or update a description for your custom resources.

Discipline
  • ...

ResourceType
  • Acceptable Value(s):
    • Null
    • Audio Book, Book, Book Series, Database, Journal, Newsletter, Newspaper, Proceedings, Report, Streaming Audio, Streaming Video, Thesis/Dissertation, Unspecified, Web site
  • This field can be used on uploads for the publication type for your Custom Resources
  • If you attempt to upload a Resource Type that is not supported, the value is ignored and the upload is continued.

PackageContentType
  • Acceptable Value(s):
    • Null
    • Aggregated Full Text, Abstract and Index, E-book, E-Journal, Print, unknown, Online Resource
  • ...

HideOnPublicationFinder
  • Acceptable Value(s):
    • Y
    • N
    • Null
  • Titles that have a Y in this column are hidden from view in Publication Finder.
  • This field can be used to hide both custom and managed titles.

Delete
  • Acceptable Value(s):
    • Y
    • N
    • Null
  • Titles that have a Y in this column are deleted during the upload process.
  • This will remove only the specific instance of the title. Instances of the title with different Sources would be deleted using their own rows.
  • This field can be used to delete both custom and managed titles.
  • If left blank, N is assumed.
    Note: You can also "delete" managed titles by de-selecting them in the Title Wizard.