Ryan Wick

QA that this is an option to set Visibility for the whole importer, or if you specify it per-work in a CSV upload that the values are understood.

Believed to be complete, reworking of verification tasks for newer content is happening in newer tickets such as https://github.com/OregonDigital/OD2/issues/3031

Metadata Team to review if this is needed for MVP, weighed against current data and lack of ordering.

I saw today that this occured again on several collections, `osu-scarc`, `osu-historical-publications`, `siuslaw`, and `aerial-photos-mid-willamette`. These are definitely ones we've been ingesting into with bulkrax. There were a few hundred...

The labels in the facets should appear as they come from the vocabularies. We can't force capitalize everything. The actual value that is indexed and faceted on can be normalized...

@jsimic @shieldsb @CGillen I don't think this is acceptable. This looks horrible:  Is there no way to only capitalize labels that are lowercase and retain any existing capitalization?

I can't get tests under Docker to run. `docker-compose run test rspec` gives 'Failed to open TCP connection to localhost:9999 (Cannot assign requested address...)

Also I don't think we need all of those binstubs, I'd just keep the ones we're actually likely to use.

"The property skos:related is used to assert an associative link between two SKOS concepts." Maybe if we're wanting to include external URIs and concepts that may not be SKOS concepts,...

Definitely need to block `.` in the ID. The term will be created, show up in Review, but then 'can't be found' when you click the link in Review.