Validation for Metadata Requests
While testing copy-absolutes I found that if I make a request for a specific starttime, endtime and observatory to the staging metadata database, the request will always return a Reading metadata for the requested observatory with a null starttime and endtime instead of the metadata that already exists with the requested starttime and endtime. Reading metadata with null starttimes and endtimes should not exist in production, however this behavior is still questionable.
We should discuss how the MetadataDatabaseFactory.py works and whether or not we should implement some validation methods for requested and returned metadata.