Evaluate staleness of hydra-pcdm/hydra-works tickets

[tpendragon]

No description provided.

[jrgriffiniii]

samvera/hydra-pcdm#53 doesn't seem unreasonable. I'm not certain if this should be considered stale, but it seems as if there was a consensus at the time.

[jrgriffiniii]

samvera/hydra-pcdm#95 might need to be created for active_fedora given that it addresses https://github.com/samvera/active_fedora/blob/master/lib/active_fedora/with_metadata/default_schema.rb#L8

[jrgriffiniii]

https://github.com/blancoj/hydra-pcdm/tree/issue_145 needs to be rebased, but samvera/hydra-pcdm#145 still may be a valid refactor proposal.

[jrgriffiniii]

samvera/hydra-pcdm#177 also needs to be created for active_fedora.

[jrgriffiniii]

samvera/hydra-pcdm#184 needs to be created for hydra-works or hydra-file_characterization

[jrgriffiniii]

https://github.com/duraspace/pcdm/pull/4/files#r31881404 was merged, so samvera/hydra-pcdm#217 still looks to be valid.

[jrgriffiniii]

My suspicion is that samvera/hydra-pcdm#245 is strictly concerned with Hyrax behavior, but I've enquired within the #hyrax Slack Channel in order to confirm that this is indeed the case.

[jrgriffiniii]

samvera/hydra-pcdm#266 might be unnecessary, as the coverage is currently reported as being at 99%: https://coveralls.io/github/samvera/hydra-pcdm

[jrgriffiniii]

samvera/hydra-works#315 seems to have had a solution with samvera/hydra-works#317, but it was closed without any explanation.

[jrgriffiniii]

@mark-dce has volunteered to review the issues created for hydra-works in response to this, and will delete or confirm the importance of these.