English > Support
AllRovi movie script
minolotus:
--- Quote from: Ivek23 on August 05, 2011, 07:52:23 pm ---"Added" field does not change, remaining from the date of entry when the entry was added, while in the "Modified" field is changing the date in it with every change made to any of the saved in PVD database.
--- End quote ---
My point was that the format of the date of the "update" field on the one hand and the "modified" and "added" fields on the other hand are not the same due to the local date settings on my computer. The structure of the update field is "YYYY-MM-DD" and the structure of the other fields mentioned are "DD.MM.YYYY".
--- Quote ---What about the custom "Updated" field, there are certain data change.
See attached pictures.
--- End quote ---
That's true. The "update" field works fine. But it is important for me that the "modified" filed is updated every time when changes on the data are proceeded.
rick.ca:
--- Quote from: minolotus on August 05, 2011, 07:23:49 pm ---Unfortunately, the date format is not similar to the date format of the "added" and "modified" fields. Would it be possible that the fields use the local settings of the respective computer?
--- End quote ---
The script engine includes the necessary date-handling functions, but it's not possible to add a custom date-type field to version 0.9. It is in version 1.0, so we can make that change when it's released.
--- Quote ---I have another issue with the "modified" field. I am not sure if this is related to the script or a more general problem of PVD. I rerun the script to get the synopsis to a custom field. The script put the data to the field but the "modified" field wasn’t updated. I checked this with the "characteristics" and the "flags" field (removing the data and rerunning the script). In both cases the "modified" field wasn’t updated?
--- End quote ---
This is curious. If I change any fields (e.g., removing data to see what happens when the script is rerun), Modified is updated (i.e., immediately—before the script is run). I don't know why that might be different for you. In any case, the main program handles the date fields. Whatever is happening has nothing to do with the script.
--- Quote ---But it is important for me that the "modified" filed is updated every time when changes on the data are proceeded.
--- End quote ---
As well you should be, if using PvdImport to update J. River Media Center. It relies on an accurate DateTime to determine which records have been updated by PVD. I haven't noticed any problems with records failing to update. Have you?
minolotus:
--- Quote from: rick.ca on August 05, 2011, 08:42:28 pm ---The script engine includes the necessary date-handling functions, but it's not possible to add a custom date-type field to version 0.9. It is in version 1.0, so we can make that change when it's released.
--- End quote ---
Thanks, that's great. Looking forward to it.
--- Quote ---This is curious. If I change any fields (e.g., removing data to see what happens when the script is rerun), Modified is updated (i.e., immediately—before the script is run). I don't know why that might be different for you. In any case, the main program handles the date fields. Whatever is happening has nothing to do with the script.
--- End quote ---
Are you sure that the update of the field is caused by the rerun of the script and not by removing the data before? I check this with the imdb script and I think that the timestamp is set after the update?
--- Quote ---As well you should be, if using PvdImport to update J. River Media Center. It relies on an accurate DateTime to determine which records have been updated by PVD. I haven't noticed any problems with records failing to update. Have you?
--- End quote ---
Yep, when the "modified" field is not updated, PvDImport does not recognise the update and doen't import the new data. Then, I need to start the update manually :(
Update: I have just remembered that I had similar problems with the multiple movies editor:
--- Quote from: minolotus on May 28, 2011, 03:31:12 pm ---I have discovered that the field “last modified” is not always updated when using the multiple movies editor. This appears only from time to time. Maybe the problem is related to the field to be modified. When I change the genre, the timestamp does not change but after editing the director field of the same movies the “last modified” field is updated.
--- End quote ---
rick.ca:
--- Quote ---Are you sure that the update of the field is caused by the rerun of the script and not by removing the data before? I check this with the imdb script and I think that the timestamp is set after the update?
--- End quote ---
Modified should be updated whenever any data changes for any reason. I've never had reason to care, but it actually improperly updates if a record is put in edit mode and no changes are made.
Although I haven't tested all fields, I haven't noticed or found any that don't cause Modified to be updated when they are changed by directly editing the record. Have you? Which fields?
Although I haven't tested all plugins and scripts, I've never noticed Modified not being updated when one is run.
--- Quote ---I have just remembered that I had similar problems with the multiple movies editor:
--- End quote ---
I can reproduce this. I haven't attempted to determine whether fields other than Genre are affected, or whether or not it happens consistently. From what I'm seeing, my guess is the problem is restricted to the MME.
--- Quote ---Yep, when the "modified" field is not updated, PvDImport does not recognise the update and doen't import the new data.
--- End quote ---
This observation doesn't shed any light on the matter. If Modified has not been updated by PVD, PvdImport is not supposed to re-import the data.
--- Quote ---Then, I need to start the update manually
--- End quote ---
What do you mean by this? If Modified hasn't changed, you would have to force an update by using the "Send to" menu or run another "Mass import."
minolotus:
I did some tests to narrow down the source of the problem but this wasn’t really successful. I couldn’t discover a pattern in the behaviour of the “modified” field. Here are some of my observations:
- The problem is not related to a specific script or to the import by scripts in general. The problem could occur with the imdb script and allrovi script, the MME and also in the manual edit mode.
- I tested also with a new and clean database therefore this should not be problem with a corrupted database. Further I switched between local access to the database and connection to the firebird server but this did have any affects on the problem.
- My movie skin could be blamed as I tried this also with a standard skin of PVD.
- There are some fields which causes never any problem, i.e. Budget, box office. When updating the data with a script, deleting or editing the entries manually the “modified” field is updated.
The problem seems to be connected with specific movies as well as with specific fields. Please find attached a table with my testing for four movies. There are some actions which causes always problems (update sub-genre and characteristics with allrovi script). Some other problems occur only for movie 2 and 4. ???
[attachment deleted by admin]
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version