Adding movies with Pre-fill active

Movies CLZ Movies Mobile
1

Hi.
I add movies to my collection with the Pre-fill screen active for most of the fields available. This is a procedure that works for me and there have never been any problems for me, until today.
This leads to some questions about this feature.

  1. Just wondering because this happened today, if a Field is empty in pre-fill should it remain empty or should it get data from Core if such exists? Earlier the field remained empty (as I remember it) but now data from Core appears.

  2. If the Field is a multi-value field and the data in pre-fill is different from the data in the Core, does the feature ignore the data in the Core or does it get added to the pre-fill data? Example: Subtitle field, pre-fill is set to English but the Core also have French and Spanish. Does this give the result English or English, French and Spanish?

2

If you leave a pre-fill field empty, and we have something for it in Core, it will download that information from Core and enter it in that field. That is how it’s intended to work, and that is also how it works when I check on iOS and Android.

For multi-value field, it will grab whatever you put in that field if you put something in (leaving it empty will do what I wrote above).

So in your example, it will add English only.

3

Thanks for the answers.

So in other words my only option to keep a field empty is to edit it after adding and then never use ‘Update from Core’ (since this will write the data back).

Since Pre-fill is an active choice by the user (to use/not use, which fields to use and the data to fill), it feels more logical to me that an empty field in Pre-fill should remain empty. I could have removed the field from the Pre-fill preset and the outcome would be the same.

Why I nag about this is because I have an issue with that the Edition field often have junk data and I think it smoother to remove this data in the adding process by having this field empty in pre-fill and only fill it with the data I want to have in there. This way I don’t have to make an extra edit later on to remove the unwanted junk data.

Examples of junk data in this scenario is that the Edition field in the Core have data that is more appropriate for other fields such as ‘Blu-ray’ (totally unnecessary because there already is a Format field), ‘1-Disc’ or ‘Single Disc’ (already exists a field for no of discs that should be used)

4

I understand your argument and I’ve noted it.

For now if you want you could just put a . or something in the pre-fill field for it, which makes it “filled in” with a .

That way you won’t get any data in those fields.

Keeping the field empty if the user uses it in pre-fill and leaves it empty because a field “often” contains junk sounds like a remedy to a bigger problem where we should fix that we don’t provide junk though :slight_smile: . Edition field indeed often contains stuff like “Blu-ray edition” which isn’t nice. Will make a note about that too.

1 Like