-
Notifications
You must be signed in to change notification settings - Fork 0
Site0001
gonter edited this page Jan 15, 2012
·
11 revisions
- name of project: unknown
- sponsor/requested by: Susanne
- class: literary resource catalog
- title: ?
- rights: ?
- original environment: supposed to be WIN95, but it seems as if it is plain vanilla MSDOS 6.x or lower. (yeah, let's talk about long term preservation right now!)
found at this excavation site:
- one .EXE file plus a couple of binary files
- *.DAT seem to carry the actual data, that is TIT.DAT and PERS.DAT
- several other files named
m/{TIT,PERS}\.[IE][0-9]/
which seem to carry some kind of index; these are not really relevant, as far as I can tell right now.
- Files seem to be encoded in CP437
Code | Meaning |
---|---|
0xFF | seems to indicate a record separator |
0x01 | seems to indicate a sub-record separator |
0x00 | seems to indicate a field separator |
code | TIT.DAT | PERS.DAT | Comment |
---|---|---|---|
0xFF | 1 | 524 | record separator? |
0x01 | 3165 | 671 | sub-record separator? |
0x00 | 45000 | 6629 | field separator? |
0x0D 0x0A | 3165 | ? | end-of-line/end-of-record? |
0xDB | record filler? |
starts with: 0xFF "000 620.005" 0x00 (that's 11 bytes)
starts with: 0xFF "000 1.100" 0x00
the DAT files data fields seem to be strings which are structred by the application, so this is outside of the scope of the perl module "DBF::Unknownw";
- seem like librarians have been at work here, each (sub-)records looks like this (first entry from PERS.DAT):
{
'fields' => [
'000 1',
'100 Achleitner, Karl',
'110 Karl (Carl) Kellnarn',
'120 *30.10.1859 Braunau (O<99>)',
'130 +17. 12. 1914 Senftenbach (O<99>)',
'140 GG; Kosch 3; AK',
'150 Lehrer'
],
}
- each field carries some three-digit numerical field code (MAB?), followed by the string representing it's content.
- 000 indicates the record number, "001" is it's value in the example above.
look at these items
- "000 114.100 Ehmann, Helene"
- "Bancalavi, Gustav"