The scale was created specifically for this project – it’s not part of our internal systems.

I’ve been trying to create a similar quality of records scale for our own internal use and I think that publishing this information is a really interesting and cool idea. Especially in terms of prioritizing data cleanup projects this kind of tool would be really helpful. Unfortunately we don’t have the ability at the moment to evaluate approved/vetted for individual fields, only for the entire record.

Was this scale a new creation as a part of your ‘open the floodgates’ project or was something similar already in place that was for internal use only?

Best,
Scott

I had mentioned in the post the reason for the change of policy, so I won’t reiterate that here. In terms of the current policy, we are holding back the record if there are fewer than three fields populated. With just two fields, the information seemed frustratingly too little to do much good. However, over time, our thoughts on that may change as well as we see how people use the database.

I find this very interesting! I work at the Maritime Museum in Sweden and we are currently working on “opening our floodgates”. I have a question for you: We are debating whether we should publish all of our database posts, even the ones where we have very littleinforamtion, or if we should just open the floodgates and display everything. Was this a difficult question for you? What made you decide on publishing everything?

Best regards

Johan Löfgren