CSV List - The definitive KK Photo Story, Magazine Story & Film Story data
 

Data format
 

Let's pause for a moment and see where we are.

Rob4 started this topic to "try and organise the identification of all the female models" in the *****climax.com sets. This is a good objective, but I think it should be part of a much larger CC database containing mag, film, video and internet info.

This "complete CC" database is impossible for one person to create, so we need to share the workload, like in this topic. We also need to share our data in a format that is easy to read and easy to use in databases or spreadsheets.

The best format is plain text in comma-separated values or CSV format. I asked Rob4 if he could change his data to CSV format and he kindly agreed (see post #1). I know that it was a lot of work for him. I ask that other people use CSV format.

I think it best to have two sets of entries, one for Set/Story Title/Magazine and the other for Set/Actress:
___________________________

.Type, CC Set, CC Category, CC Story Title, CC Pics#, Original Mag.Story#, Comments

.Type: . followed by one-letter code for data type, use .P (for Photoset or Pics)
CC Set: code on website, use lower-case letters, e.g. 84i, not 84I
CC Category: two-letter code for studio on website (CC, BC, SG, LL, AS, SB, TC, CG), leave blank if not known
CC Story Title: title on website
CC Pics#: number of pics on website, leave blank if not known
Mag: two-letter code for original mag (AS, BC, CC, EX, LL, MC, NC, RO, SB, SG, TC, TS) followed by mag number, use ? if not known or leave blank
Story#: number of story in mag, use ? if not known
Comments: special comments about the photoset only (not the story or actresses), leave blank if no special comments

Example
.P, 84i, SB, Kinky Game, 22, SB72.2,

(Set 84i is in Sex Bizarre studio on website, has title "Kinky Game", contains 22 pics and corresponds to second story in Sex Bizarre 72 mag)

(icu has provided a lot of this info already)
___________________________

.Type, CC Set, CC Name, Professional Name, Sex Action, Comments

.Type: . followed by one-letter code for data type, use .A (for Actress or Actor)
CC Set: code on website, use lower-case letters, e.g. 84i, not 84I
CC Name: actress name used on website, use ? if unknown
Professional Name: better-known name of actress, use ? if unknown
Sex Action: performed by actress, such as A (for anal) or DP or GS, separated by semi-colon ;
Comments: comments about actress as she appears in the story (but not sex action)

Example
.A, 84i, Barbara, Daniella Rush, A;DP;GS,

(Daniella Rush is called "Barbara" in set 84i and does anal, DP and GS)

(Rob4 has provided a lot of this info already)
___________________________

Other thoughts:
* I think colour is not necessary. It takes too long to do. When the text is copied to an editor such as Notepad, colour disappears anyway.
* I have no interest at all in actor names.
* Links to egafd or bgafd or elsewhere in VEF could be provided when people click on Professional Name, but not for well-known IDs. When the text is copied to an editor such as Notepad, link info disappears which is OK.

Ok, it's no problem for me to reformat my listed content for the entries ( VB - Routines ).

In the first step I save the entries without mag-infos.

example:

84i, Kinky Game, SB

The unknown sets starting with 'set' and '5' have to be modified later.

icu

icu, please stop re-formatting. I have thought of something else!

I think the CC Studio info is useful to have as a separate field. Therefore change

CC Set, CC Story Title, Mag.Story#

to

CC Set, CC Studio, CC Story Title, Mag.Story#

For more details, please see post #103 above.

____________

icu,

Sorry to mess you about. Please leave Mag.Story# blank if you do not know the mag, but make sure there is a , after CC Story Title. Many thanks. :)

@ fannatastic

Just to understand what you're proposing an ID example:

14f, CG, Musical Seduction, 22, TS05.3
14f, Hanne, Hanne(CC)
14f, Yvonne, Uschi(CC)
14f, Trine, Mikki(CC)

Is that ok?

What's the advantage of separating Story/Mag ID from Actress ID by extra lines?

I think the number of pics in each set is useful to have as a new field. Therefore change

CC Set, CC Studio, CC Story Title, Mag.Story#

to

CC Set, CC Studio, CC Story Title, CC Pics#, Mag.Story#

For more details, please see post #103 above.

I hope this is the final change to CSV format, but who knows for sure? :)

Second field should be AS for all of these entries. In other words, instead of 13c_AS have 13c, AS.

By Studio I meant the studio section on the website, not the actual location of the shoot.

The idea is that we could list all the sets in numerical order and still know which "studio" they came from. The "studio" info helps (sometimes anyway) when searching for the correct mag.

Sorry for the confusion.

We need an ending item to separate optional comments like second or third mag.

Only to confirm a sample :

15a, AS, Black Arse Buster, AS82.?

your variant with the studio will fasten it , I'm writing some VB-Routines to export the linked mag titles I know.

*** Problem solved *** Post is ready to be deleted

icu

Yes, except I prefer:

14f, CG, Musical Seduction, 22, TS5.3

The advantage of separating them is that the number of fields is always the same (five and three), no matter how many actors/actresses appear in the story. This would not be true if everything is in one line. It is important for the CSV files to have a fixed number of fields.

The disadvantage is that it is not possible to tell from the first field (CC Set) if the entry is CC Set-Mag or CC Set-Actress. Therefore, the two must be kept in separate files. A solution to this problem is to add another field at the beginning, e.g. A for actress to CC Set-Actress, e.g.

A, 14f, Hanne, Hanne(CC)

But what letter(s) to use for CC Set-Mag? M/F/V are no good, because these are needed for the mag/film/video section of our "complete CC" database. ;)

With a new prefix, the data could be stored in the same file.