I used the late, great, lamented Circus Ponies Notebook for all kinds of notes and record-keeping. I have a data set I would like to port to Panorama X. Any suggestions on how?
The outline is set up with unique top-level alpha-numeric identifiers. Each top-level identifier (the Parent) has children: always an image, one or more aliases for the top-level identifier, and my text notes. There may be up to 20 of these child-items. Some child notes have child notes of their own.
The fields I’d like to end up with are at the very least:
- Top-level identifier
In NoteBook, what I currently have was set up for ease of use:
I am consolidating collections of photographs. The images have information in their filenames, but the information is coded in different ways (more or less: Roger, Rog, RD, RDoe, etc.). One of the ways I want to use the PanX version of the dataset is to query it for the new unique ID and add this a prefix to the file names (“RD01”). At the most basic, I want to turn my outline into a look-up table.
My thought is to flatten the outline to a table and import that. The columns would be:
- Unique alpha-numeric ID
- Unique human-language ID
Which brings up a difficult (for me) question:
Is there a better structure than simply having as many fields for Alias/Collection pairs as I need? Note that the Aliases are not unique and are, in effect, unlimited. The Collections are unique and are quite limited (twenty now, almost certainly won’t exceed 50). Each “Alias/Collection” pair is unique. Currently I have about 600 unique top-level identifiers, and 3,000 Alias/Collection pairs. This represents the bulk of the data I intend to use for this project.
Thanks for reading and considering.