ID Projects, ID Sheets & ID CSVs ( *** Discussion *** )
 

hi folks

i want to start putting down some permanent names on models already identified but known under more than one name. these are the first two i want to deal with. i'll say what i think then anyone else can come in with an opinion and hopefully we will come to an agreement.

.A, 1296a, Marta, Monica Sales, , aka Thunde
.A, 1296c, Gigi, Solange Yi Lon, ,

Solange Yi Lon has a thread here under 'Solange Hop' and her main entry at egafd is 'Solange Hop' therefore I will change it to that if no one objects.

Monica Sales does not have a thread, but is known as 'Thunde' at egafd, therefore i will again change it in the list unless someone has a good reason to keep it as MS.

Re: Name Changes
 

Hi Rob
I think firstly you need to decide rules for deciding on which name should take precedence for a models screen name, eg. imdb, egafd, wikipedia, models own website. In an attempt to avoid future arguments as to whick of a models aliases to use.

Secondly I think that a csv just listing model names should be constructed (I'm happy to start work on one) proposed format:
.SN, Screen Name, Birth Name, Birthdate, Birthplace, Gender, Comments, aka1, aka2, akaN

Where "Screen Name" is a unique name we decide on using for the Model (given our naming convention).
Birth Name, Birth Date, Birth Place will not be known for many actresses but I see no reason why this information shouldn't be included.
Comments can be things like external links to listings in IMDB etc. although this info could be contained in a seperate list?
And finally any aliases for the actress

This way all publications (image sets, mags, film, and playing cards) can link to a unique name without the current concurrency problems.
BB

I aggree to a CSV ( it would be very useful for longer or combined aka names imo ),

but I have to disagree to post personal datas like 'Birth Name'. No datas should lead direct to a real person.

The CSV should have a static format - all akas should be separated in one cell perhaps with a ';'

Please see the Actor category here.

This has existed for a long time and I think now is a good time to start using it. The format is very similar to BB's suggestion. Comments should be the last field always. I added the Aliases field today. I have no problem with Real Name, but this could be left blank if people object to it. (Very few real names are known anyway.)

The logical Type for Actor is .A and so the existing .A list should be renamed .PA (for Photoset Actor).

I tend to agree with you, some birth names are so well known that it would seem harmless to include, however some may not be well known and I don't think we'd be able to formulate rules for when we should include the info and when we shouldn't, there are nutters out there and we don't won't to aid them.

Simple, easy to implement, nice suggestion!

Having given this a bit more thought I think a links field should be added seperated by semi-colons ; destinct from the comments field.

Finally, whatever name is assigned for the ID field should not be changed EVER.

i did have rules for this but there has been some slippage. the rules were that for usa/can/south america iafd would take precedence, for uk bgafd, and the rest of europe egafd. any others would have to be agreed upon.

however the biggest hurdle and the main cause of the slippage is that egafd/bgafd and even sometimes iafd change the main identification name based on the number of appearances under that name they have listed. this often leads to use of generic names like georgina, tina, etc, etc or names that are different to the most commonly known names. there are also a few that don't appear on the websites eg 'Zoe'@fiona cooper.

i agree that once a name is decided it should not be changed but that rule can't stand in all circumstances. for instance i don't think 'Barbara' can be left as 'Tina[16]'@egafd should a more unique identification turm up.

i don't think we can get this naming perfect but it does need to be agreed and the only way i can see this happening is to go through each of the names and agreeing the ones that can remain as a permanent id and then identifying the few that may possibly change in the future.

we also need to find a way of 'labelling' all the cc classic girls that don't have a current cc classic name.

i see nothing wrong with this except that aliases in some cases will go on forever - Maria Szolontai anyone? and by the way that is one that has changed the main name also!
http://www.egafd.co.uk/actresses/details.php/id/m0177

Just wondering what the cut-off point is for being described as "CC Classic" because I wouldn't have thought that Lilly would qualify as her sets were published 1989-1992.

Yes although we have not defined the cut off point for cc classic i think there is a good chance that a video id will turn up for her, which is why I haven't added the Lilly id yet. This was also the reason for not using 'Barbara' for Tina[16]. and I was also reluctant to use 'Beth', but was less certain anything better would turn up for her.

There was definitely a stylistic change for the photosets around the early to mid eighties. i think somewhere around there should be the cut off point. i'm happy to take guidance on someone in possession of the magazines themselves to advise on this?

Jens Theander quit in the summer of 1985, then the Candy Film Studio was shut down in 1986, but the use of homegrown Danish stuff had stopped even before he left.

Actor CSV format
 

Actor category is currently defined here as follows:

Actor
Type
ID
Gender
Professional Name
Aliases
Real Name
Date of Birth
Place of Birth
Nationality
Comments
______________________________________

Proposed future Actor format:

Actor
Type
ID
Gender
Professional Name
Aliases
Date of Birth
Nationality
Links
Comments

Notes
Professional Name: best porn name that we here at VEF prefer.
Aliases: only important and widely used Aliases should be listed, e.g. Ramona Kassel for Desiree Barclay or Denise Remplace for Dagmar Lost.
Real Name: deleted.
Place of Birth: deleted. No need for this and Nationality.
Nationality: this could contain Country data in fact, e.g. USA or UK or Hungary, not American or British or Hungarian. Whichever is chosen, Nationality is a good title because first letter of each field title is different. Could use shorthand country codes to save space, similar to mag series codes.
Links: field added for http://... links, with multiple links separated by semi-colons. Other categories would benefit from having a Links field, but it may be better to add Links data in the future to avoid clutter. In other words, subsets without Links could be used for the time being.

All comments welcome. :)