Too Many Dev Glosses

[thehabes]

Testing the various Gloss List and Gloss List Item templates can be very time consuming. At the time of writing this issue there are nearly 600 Glosses on dev. This occurred because at one point we took the data from prod and replicated it on dev for some real situational testing.

Now, though, this has become cumbersome for developers. Testing changes to these templates sometimes means refreshing the cached Glosses. Developers should not have to wait 5-10 mins to see if their template changes worked or not.

The reason these interfaces find all of the Glosses is because these kinds of Annotations are placing Glosses into the "GoG-Named-Glosses" collection.

{
	"@type": "Annotation",
	"target": "https://devstore.rerum.io/v1/id/614362c3e74876243131a4e0",
	"body": {
		"targetCollection": "GoG-Named-Glosses"
	}
}

If we want to reduce the number of Glosses that the applications finds when it is staged as dev we will need to delete a number of these Annotations. For those Annotations which we delete, we will need to make sure their target URI is not in the "public list" of available Glosses or this will action will cause bugs.

A reusable function could be produced to trim these down as needed. We will reproduce this situation periodically and so may need to be able to bail out at the same rate.