Problem: OA badges appear on assets even when neither the asset nor a file or link is designated as OA. This misrepresents the meaning of OA to simply mean “free to read,” and may be incorrectly applied to works to which the creator reserves rights and are not true OA as understood in the community.

Solution: Change the logic as follows:

• An asset should have the OA badge only if a file or link is explicitly affirmed as Open Access, or if the asset itself is declared Open Access.
• Files or links with no value (blank) under access restrictions should be unrestricted but not entail an OA badge (unless OA status is declared at the asset level).