Search results for: “kbart”

5.3.2.2 Publication title Give the full name of the publication, for example, as it appears on the print edition or on its web homepage. Special characters should be encoded […]

The content provider should include the following fields as columns in the tabseparated metadata file. All fields should be considered to be mandatory if they exist, and all effort should […]

5.3.1.1 Content providers should provide metadata formatted as tab-delimited values. This is a generic format that minimizes the effort involved in receiving and loading the data, and reduces the […]

5.2.1 Method of Exchange Content providers should post holdings data to a website or FTP site for download by link resolver suppliers. This minimizes the effort involved in […]

For those content providers that already provide metadata files to knowledge base developers (for example, in OAI or ONIX-SOH format), this set of recommendations can be used as a […]

Many content providers and knowledge base developers are already successfully exchanging metadata, and this report is not intended to detract from or interfere with such existing processes. However, it […]

Core problem: Holdings data generally shows the broadest range of dates available to all customers, rather than just the titles and dates available to a single institution. […]

Core problem: Outdated holdings data leads to inaccurate presentation of data. User impact: Data presented in knowledge bases is only as accurate as the data […]

Core problem: Data errors or non-standard exchange of data can slow the incorporation of that data into the knowledge base. Data that does not conform to previously agreed-upon […]

Core problem: Knowledge base developers are often uncertain as to how to apply varying embargo terms, as the same terms can be used by different content providers in […]