Develop rules for BCO scoring about bco_api HOT 5 CLOSED

Scoring might look like this (but with a more polished UI instead of text-based):

0---------------1---------------∞
----------------------^ Your score: 24

Where 0 - 1 is unvalidated territory, and anything above 1 is validated and getting a score.

from bco_api.

Possibly break it into two scores: BCO score and FINDability score. FINDability looks for things like resolvable addresses (Chinweoke's idea).

from bco_api.

Measurable Attributes

• Check for duplicates. For example in intermediate I/O steps, *this idea will be finetuned as some steps may have inputs from a previous step's output
• Open Source validation when it comes to resolvable addresses/URLs
• Usage metrics*: May not be implementable, but the idea is to gauge how people are interacting with a certain BCO

from bco_api.

#330

from bco_api.

#328

from bco_api.