Get involved in Repair Data with MobiFix! 🐳

[Monique]

@Ian_Barnard

One minor buglet asking for translation of sembla que all� on s’endolla est� xafat i no puc carregar la bateria gave a blank page on oogle translate.

Ah, that string has some non-printing characters which would explain why it was not an acceptable param in that URL.

@Ian_Barnard

One suggestion for future things like this - might be useful to put a record id on the page so it’s possible to refer to e.g. ‘number 1201 has a problem with translation’.

I’ve been thinking that too.

@Ian_Barnard

Also maybe mobifix is testing my consistency but I seem to return to the same record relatively often and having an id visible would either reassure me that’s not the case or confirm my suspicion IYSWIM.

Indeed these early microtasks have no way of checking for duplicate presentations but it is on the card for work this sprint and the next. Although tbf there are a lot of mobile records that appear duplicate but actually aren’t, they just have the same brand/model and problem text. I ran a few queries and found that I gave 113 opinions and saw 2 of the same record 2 times. The more opinions you give the more likely you are to see dupes and as we get fewer to choose from - records with majority opinions are eliminated - you are also more likely to see dupes. Working on testing an idea to workaround that.

Most people give way less than 100 opinions, about 4 people have given in the region of 200 and one person has dedicated their time to about 850!

[Ian_Barnard]

Just saw “needed new connector - professional help” twice in a row, but maybe there are two of those? Also had “0.2kg” twice today (answer: Unknown) and IIRC several times before. I guess the priority should be to ask me about the record with fewest opinions (or randomly if there are several with the same lowest number of opinions), excluding those I’ve already given an opinion on (as there’s little point asking me twice about a record). That means you have to record users who have given an opinion on each record, or maybe when it hits 3 then you can erase the user IDs?

[Monique]

@Ian_Barnard

Just saw “needed new connector - professional help” twice in a row, but maybe there are two of those?

That sounds like the same record twice.

@Ian_Barnard

Also had “0.2kg” twice today (answer: Unknown) and IIRC several times before.

There are a bunch of these with the weight in as problem text, they come from the same group years ago.

@Ian_Barnard

I guess the priority should be to ask me about the record with fewest opinions (or randomly if there are several with the same lowest number of opinions)

This is how all of the microtasks currently work - ‘fetch a random record that has not yet gained a majority of opinions’.

@Ian_Barnard

excluding those I’ve already given an opinion on

This is not something the microtasks cope with currently, see below.

@Ian_Barnard

That means you have to record users who have given an opinion on each record, or maybe when it hits 3 then you can erase the user IDs?

The majority of microtask users appear to be anonymous - either unregistered or not logged in and analytics shows that its not uncommon for users to start it anonymous and then log in. So I’m going to try collecting the record id’s seen by each user in their session variable and then exclude those id’s in the fetch query. Ofc this means that you might see the same record if you change device, IP address, logged-in status or if the session expires (I think the session duration is quite long though for the same device/IP). However, it will be the next microtask not this one (yet). If successful it could be retro-fitted to the existing apps.

Should also point out that the user has the option to not give an opinion and “Fetch another” if they’re sure it’s a duplicate although I’m usually too in the zone to remember to do that myself!

[Ian_Barnard]

@Monique

‘fetch a random record that has not yet gained a majority of opinions’ .

Call me a pedant if you want, but that’s not the same thing as the/a record with fewest opinions.

Anyway we’re so close with this one thanks to your excellent work. Please don’t think I don’t appreciate your efforts!

[Monique]

@Ian_Barnard

Call me a pedant if you want, but that’s not the same thing as the/a record with fewest opinions.

A majority is only 2 matching opinions out of a maximum of 3 opinions. So any record that has yet to achieve 2 matching opinions can be shown to a user. For the record, MiscCat had a max 3 opinions and FaultCat went with max 5. We are as always assessing our choices with regard to the parameters.

@Ian_Barnard

Anyway we’re so close with this one thanks to your excellent work. Please don’t think I don’t appreciate your efforts!

No worries, we all certainly appreciate all of your efforts and feedback! I love the discussion and the arguments here and have certainly taken a lot of it on board!

[Janet]

We are working on a list of community reuse projects, some of which accept mobiles, and can be trusted to wipe them.

I believe there are also credible corporates that wipe phones, but it requires some investigation. It depends on your personal risk threshold. Do you want data deleted immediately? (For example, we’re not certain that Mazuna wipes mobiles in the UK or merely does a triage here and exports them for data deletion…)

As we say in our Wiki

Restoring to factory settings will hide these from an opportunist but much or all of the information may still be recoverable with forensic tools, which criminals may well be in possession of.

We may not want to say this, as not sure this erm, effectively allows for reuse and recycling. Also, erm, lithium battery? @philip

Restoring to factory settings should then be effective, but even so, if you’re worried you might want to finish the job with a hammer!

[Monique]

So, we are done! Big thanks to all who particpated!

We’ve not achieved a completed microtask before so I guess it was inevitable that the final state is not handled and now loading the page results in an error, oops! Lesson learned!

We’ve got a little work to do to adjudicate , analyse and report

[james]

A big thanks again to everyone who took part in MobiFix.

We’ve now written up the results here:

Insights: Mobiles and faults - Open Repair Alliance

Oh, and you’ve all earned a special mobifix badge!

Did you know that you can use most badges as titles on the forum? Simply head to
your account preferences and choose one from the ‘Titles’ list