Investigate options for alternate_id usage [placeholder]

[eporter23]

When we implemented our locally defined NOID scheme, we learned that the Valkyrie implementation of doing this results in an additional, separate Fedora object getting created for Collections, Works and Filesets. This will heavily increase our Fedora object count, which could be a concern for performance.

To investigate:
Could we define our own distinct attribute to store the locally minted NOID (and bypass alternate_id)?
Can we determine why Valkyrie doesn't set our locally minted NOID as the actual ID, instead requiring the UUID?
Can we determine why we can't just store the string value of the locally defined ID in Valkyrie?
If we make changes, what additional work is needed to support our local IDs and persistent URLs?