T O P I C R E V I E W |
JDommi |
Posted - 12 Apr 2011 : 10:08:56 Here is a short summary of the existing Custom fields and a suggestion for new fields:
*Edit* Status of the movie like in XMB: complete/incomplete in collection, wanted, (pre-)ordered... */Edit*
C1: IMDB-TOP250 C2: Release Dates C3: Editor C4: Repository C5: Budget C6: Revenue C7: Awards (number) C8: IMDB Link C9: AKAS Titles C10: Goofs C11: Trivia
new: -Series- C12: Trivia of Season (text field > 250 chars)
C13: Character info (text field > 250 chars) should be available for every role in the movie (in later release) C14: Serie Tunes (text field > 250 chars)
C15: Status of a Series (boolean or tristate for Ended, Continuing, deposed) overlays some buttons on the edit window C16: Poster of Season (text field) - implements #TAKESEASONPOSTER# and a new category in CoverManager -Movies/Series-
C17: Original/Remake (boolean) DONE C18: Prequel/Sequel/SpinOff/Parallel (??? example: CSI) (text field/dropdown) C19: All country specific ratings (MPAA, FSK, etc.) c20: "Filmography/Movies in Database" related to a series and vice versa with link if already in db c21: chain of movies/series similar to Boxsets (Alien, Babylon 5, Critters, etc.)
|
20 L A T E S T R E P L I E S (Newest First) |
zukkara |
Posted - 07 Jun 2011 : 11:12:41 I also plead for transforming the custom fields to default fields and creating some new custom fields for the users free use. As the IMDB scipts use most of the actual custom fields, they are not free any more for personal use. In future every field should only be used for one data typ. At the moment some fields like Custom9 get filled with different information like AKA Titles and Release Infos. As a result there are headlines in the field to separate the informations. This on the other hand renders the custom9 collumn in the grid view useless, as it only shows the headline "AKA Titels" and no actual data in the field. This problem I already discussed with Prinz and JDommi in another thread here.
In the momentary situation all or most of the custom fields are occupied. For some of the fields there are options in the import scripts for some there are not. Which means that some manual inserted information will be overwritten by some scripts without the user being able to prevent it. With enough new default fields and some new custom fields this should be prevented. Scripts should allways give an option weather to write into a custom field or not. Or some custom fields should exclusivly be for personal use and not to be touched by scripts.
When can we expect the new fields? Thank you for your good work! |
JDommi |
Posted - 04 May 2011 : 07:27:09 At the custom fields: you're right. Extra3: Original - yes, but I have made a mistake on that suggestion. It had to be better to change to 3 states/combobox: original, remake, empty(normal) Character info - After having that field it came clear that this field has to be related to every actor. So this way it's useless. But have a look at the HTML Card topic page 23 for movie_bigcover: I have tried to combine both fields for the original flag. Putting info for original/remake as title and movie id (if in database) into "character info". quote: The function works perfectly. Only problem is that you have to input the original and remake(s) manually on the "unused" characterinfo field (that could be renamed/translated to RemakeInfo). If you wanna give it a try: Enter on Extra3 for any movie: Original: movie name|movieid# (where movieid is optional) and for an other movie: Remake: movie name|movieid# (multiple remakes are allowed) insert this code right above this source line: <script>add_studio_distributor_row();</script>
<a id="reminfo" style="display:none;">_MOVIE_CHARACTERINFO_</a> <script type=text/javascript> var remakeinfo = $('#reminfo').text(); var remake = ''; var myArray = remakeinfo.split('#'); if (remakeinfo.length >> 0) { document.write('<tr><td colspan="2"><b><font class="fsize1" class="style21">Original/Remake:</font></b></tr><tr>'); } for (var i = 0;i < myArray.length;i++) { remake = myArray[i]; if (remake.length >> 0) { document.write(' <font class="fsize1"><td>'); var outp = ''; if (remake.indexOf('Original: ') == -1 && i == 0) { document.write('<img border="0" src="MovieCards/Original_small.png" width="50" height="47">'); document.write('<br><b><font class="fsize1" class="style21">Remakes:</font></b><br>'); var orig = -1; } else { if (i == 0) { document.write('<img border="0" src="MovieCards/Remake_small.png" width="50" height="50">'); document.write('<br><b><font class="fsize1" class="style21">Original:</font></b><br>'); } var orig = 0; } remake = remake.substring(remake.indexOf(':')+1,remake.length); var sTitle = remake.substring(0,remake.indexOf('|')); var sID = remake.substring(remake.indexOf('|')+1,remake.length); if (sID.length >> 0) { outp = outp + '<font class="fsize1" class="style20"><a href="" onClick="window.external.COLLECTION_FINDMOVIE('; outp = outp + '' + sID + ''; outp = outp + ');return false;"> ' + sTitle + '</font></a><br>'; } else { outp = outp + '<font class="fsize1" class="style20">'; outp = outp + sTitle + '</font>'; } document.write(''+outp); if (orig == 0 && i == 0 && myArray.length >> 1 && myArray[1] != '') { document.write('<br><b><font class="fsize1" class="style21">Other Remakes:</font></b><br>'); } } document.write('</td></tr>'); } </script>
|
nehickel |
Posted - 04 May 2011 : 05:49:53 I guess the one problem I have (which is just my problem) is knowing what fields "get" populated versus what fields "need to be" populated. This is especially true with the Custom fields. Granted that it all depends on what, if any scripts are used as part of the over all movie information collection effort between user & application... but it still difficult
BTW: Anyone want to explain the new "Extra 3" page's "Character Info" field??? How is it associated with the Actor's page? If it is associated with the Actor's page, should there also be Actor ID field too??
The "Original" flag I believe is related to if the Movie is an Original or a Re-Make... Correct??? If so, wouldn't it be better on the Movie page?? Just a thought... |
JDommi |
Posted - 03 May 2011 : 19:24:19 I have a combined use of both fields as example: Repository = media box - Location = no.1 where repository has a picture. Another example: Repository: spindle - Location = 0001 The complete Custom fields (except of Custom4 for repository) are longer used for their content as I use XMM. So I don't ask if they are usefull or not. Meanwhile no. of awards as example are no longer used in my opinion, but others wanna still use it. |
KCWhiteKnight |
Posted - 03 May 2011 : 19:04:23 We actually have two fields for this. Repository and Location. I used Location to say Blu Ray Shelf or Box Shelf for examples.
Things like IMDB Top 250 are pretty meaning less to me. I don't acquire movies based on that. Something like filming locations would interest me more. |
JDommi |
Posted - 03 May 2011 : 07:24:28 Editor => Cutter of the movie. I don't know it's really long asigned to a custom field. Repository: well, for faster finding the appropriate kind and as the picture must have the same name. Normally all possibilities should have go there. Like Spindle, Box, binder, case, etc... |
nehickel |
Posted - 02 May 2011 : 23:06:44 Can someone tell me what Editor and Repository might be used for?
Why is Repository a List Box?
Thanks Norm |
JDommi |
Posted - 23 Apr 2011 : 09:48:07 Take all the time you need! (But do it *lol*) |
Alessio Viti |
Posted - 23 Apr 2011 : 05:51:04 Hello guys, I am a bit in late with these new fields, I think I need some extra time to do that
Ale |
JDommi |
Posted - 20 Apr 2011 : 11:09:21 To pick that up again: there was already a discussion about the pictures - http://www.binaryworks.it/forum/topic.asp?TOPIC_ID=6775 Would be great if there will be more categories at all. |
Prinz |
Posted - 20 Apr 2011 : 10:52:02 Screenshots would also be a good additional field.
Also that the Chapter Field should change to Memo Typ... At the moment half the info is lost on import because it's only Text (250 Chars) |
JDommi |
Posted - 17 Apr 2011 : 22:12:44 Well, that seems to be a real good idea. I think Ale will have to do a lot in the next time... |
Prinz |
Posted - 17 Apr 2011 : 21:40:15 I would be great if Ale could add a ratings-base field, so that the Ratings-bars are always correct and a magic script function in the #RATING# and #EPISODERATING# Block:
#TAKERATINGBASE#=#??#
and a movie card variable:
_MOVIE_RATEDBASE_
So every script can add its base value for the rating, since every page has a different base 5, 10, 100 and so on. |
JDommi |
Posted - 17 Apr 2011 : 13:18:02 @toycole: No, you don't have to change anything! |
JDommi |
Posted - 17 Apr 2011 : 11:53:23 Excerpt from an email by Ale: quote: About the other fields, I hope to work on it asap. First I want finish with these new, fix all bugs and then move on.
|
Mawu |
Posted - 17 Apr 2011 : 10:52:03 Hi
after "occupying" the custom fields with the IMDB stuff (which I also use), what about giving us a set of new custom fields?
BTW: C7 Awards (numbers) seems to be dispensable for me as there is a detailed listing in awards field.
Bye Byte and Happy Coding Mawu |
tonycole |
Posted - 16 Apr 2011 : 12:05:58 Hi
Will i need to edit my custom moviecard for these changes or will the fields stay the same.?
thanks Tony |
Alessio Viti |
Posted - 15 Apr 2011 : 13:03:09 Yes, the name of the variable inside the DB yes. For the MovieCards, the _MOVIE_CUSTOM_ will remain, but will be used only for these specific fields.
Ale |
JDommi |
Posted - 15 Apr 2011 : 11:11:38 Will the variable on the HTMLCards still be CustomX? A mix would not be a good solution... |
Alessio Viti |
Posted - 15 Apr 2011 : 10:57:30 Hello,
I think that is better, instead of adding the new field for the custom 1-11:
C1: IMDB-TOP250 C2: Release Dates C3: Editor C4: Repository C5: Budget C6: Revenue C7: Awards (number) C8: IMDB Link C9: AKAS Titles C10: Goofs C11: Trivia
to change their "name" in the english.ini file.
This because all scripts and all data inside the database are already filled. |