You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The specification calls for a CreationTime field in UANodeResults that reflects the time the namespace was created, presumably when it was uploaded to the cloud library. It is distinct from the PublicationDate.
In the current implementation we renamed the CreationTime to PublicationDate and some of the records in the database reflect that correctly while others return the upload time.
Proposal:
Add the CreationField back
Store and return the PublicationDate/NamespaceUri as part of the metadata. Update the specification accordingly.
OR remove the Version field from the UANamespaceResult and return PublicationDate/NamespaceUri/Version only with the NodeSet/NodeSet2 datastructure.
Clean up existing database records to be consistent.
Additional proposal (implementation only):
4. Store the predefined metadata as a well-defined database table instead of in the name-value-pair table. Leave the name-value-pair table only for additional/custom properties.
The text was updated successfully, but these errors were encountered:
The specification calls for a CreationTime field in UANodeResults that reflects the time the namespace was created, presumably when it was uploaded to the cloud library. It is distinct from the PublicationDate.
In the current implementation we renamed the CreationTime to PublicationDate and some of the records in the database reflect that correctly while others return the upload time.
Proposal:
OR remove the Version field from the UANamespaceResult and return PublicationDate/NamespaceUri/Version only with the NodeSet/NodeSet2 datastructure.
Additional proposal (implementation only):
4. Store the predefined metadata as a well-defined database table instead of in the name-value-pair table. Leave the name-value-pair table only for additional/custom properties.
The text was updated successfully, but these errors were encountered: