# baseURI: https://www.archives.gov/files/lod/dpframework/id/NF00541

@prefix : <https://www.archives.gov/files/lod/dpframework/schema> .
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix nara: <https://www.archives.gov/data/lod/dpframework/def/> .
@prefix naraid: <https://www.archives.gov/data/lod/dpframework/id/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix wikidata: <http://www.wikidata.org/entity/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

naraid:NF00541
  a nara:FileFormat ;
  dcterms:description "Btrieve 6.0 (BTR) files were created by the Btrieve transactional database program. Btrieve uses the Indexed Sequential Access Method (ISAM) to store and retrieve data. Version 6.0 of the program was not completely backwards-compatible with earlier BTR files due to the introduction of new features, but the APIs remained compatible. Btrieve has been developed by several companies over the years, with Btrieve 6.0 being released in 1992, during Novell's ownership of the software. While Btrieve still exists and has been rolled into Actian's Zen database applications, the BTR file format is proprietary and does not have an open format specification. NARA recommends transforming BTR files to a more sustainable format, such as CSV." ;
  dcterms:identifier "NF00541" ;
  rdfs:label "NF00541" ;
  wikidata:p1163 "application/octet-stream" ;
  wikidata:p1195 "btr" ;
  wikidata:p973 "https://en.wikipedia.org/wiki/Architecture_of_Btrieve" ;
  wikidata:p973 "https://en.wikipedia.org/wiki/Btrieve" ;
  nara:category naraid:Databases ;
  nara:formatName "Btrieve 6.0" ;
  nara:preservationAction naraid:Transform ;
  nara:preservationPlan "Transform to CSV" ;
  nara:riskLevel naraid:High ;
  nara:tools "Procure and/or develop tools. Any process will require Actian (formerly Pervasive) Btrieve drivers. Access can read btrieve tables only if there are data definitions available, which are Btrieve .DDF files. If there are no ddf's, the processing archivist will need to create them from scratch with either a 3rd party tool such as BtSearch or use Actian's products. With both the BTR and DDF files and the Actian/Pervasive ODBC driver to set up ODBC DSNs the data can be read ith MS Access." ;
  <https://www.archives.gov/files/lod/dpframework/schemaArchiveTeamURL> "http://fileformats.archiveteam.org/wiki/Ext:btr" ;
.
<https://www.archives.gov/files/lod/dpframework/id/NF00541>
  a owl:Ontology ;
.