The tape database is implemented by storing all fields as control sequences,
thus it is suggested that the database be constructed using reasonable-sized
files; subsequently to make tape labels, only the necessary files be
The tape database has been implemented with the aim that the database
files be sharable amongst various users so long as every album has a unique
<#63#>album-id<#63#>. In order to load a tape database, all one needs to do is
For example, one may have a file <#73#>mozart1.bum<#73#> with various album
descriptions of Mozart's compositions, each having an album-id of the form
<#74#>mozart1.1<#74#>, <#75#>mozart1.2<#75#>, and so on. If a single piece of music
spans both sides then we might label the two parts using another level of
subscripts, for example <#76#>mozart.12.1<#76#> and <#77#>mozart.12.2<#77#>.
The only problem with above conventions is that if two users have a file with
identical album-id's then the file will have to be
copied and the album-id's changed.
Following page contains an example. Commands used to generate the label would
be:
25pt
The file <#94#>example.bum<#94#> contains:
<#101#>
12]<#89#>vivaldi.1<#89#><#90#>vivaldi.2<#90#>