Data management in AP3

Question

Level 1

4 points

Data management in AP3

Rather new to AP3 I am puzzled by its file management.

Right from my first use and imports in two distinct libraries, the map "Masters" refers in one lib to the successive sub maps "2011" (to) "03" (to) "27" (to) different maps with the image files. In the second lib the "Masters" refer to the consecutive sub maps "2011" (to) "03" (to) "30" or from "04" (to) "18" (to) also distinct maps with image files.

What is the reason these sub maps don't count from the very beginning from 01, 02, 03, 04, 05 (etc.), instead of jumping from 03 and 04 to 18, 27, and 30 ?

It seems odd to me, but then - as I admit humbly - I am far from understanding many "ins and outs".

Anyway, I did not found this out in AP's User Manual or any other means of a support forum or documentation (TOO huge and disparate on the net indeed...)

(My actual OS X version is 10.6.7, and Aperture 3.1.2)

iMac11,3 (2.8 GHz Intel Core i5), Mac OS X (10.6.6), 8 GB 1333 MHz DDR3

Posted on Apr 23, 2011 7:41 AM

Reply

Answer 1

Best reply

Kirby Krieger

Level 6

12,592 points

Apr 23, 2011 7:46 AM in response to pdrcourious

Those are most likely dates. 😉

Reply

Answer 2

pdrcourious Author

Level 1

4 points

Apr 25, 2011 1:45 AM in response to Kirby Krieger

If the "dates" are these of importing the image files into Aperture, rather than the dates on which the images were taken (from the first month january on), you are most likely right. At closer look indeed, the "consecutive sub maps" I referred to seem to be the months ("03" = march; "04" = april) and days I started using AP3.

Reply

Answer 3

Mr Endo

Level 4

1,010 points

Apr 25, 2011 4:24 AM in response to pdrcourious

PDR,

Just remember that you are looking at the "internal workings" of the Aperture structure. That will very well change in the next major version, and it could change in a minor version, too. Basically, what you are looking at is "not for consumer use." That's why you did not find any documentation on it.

nathan

Reply