meta-data section in FOLIO records (createdDate, updatedDate, creator, etc)
Description
Environment
Potential Workaround
blocks
is blocked by
relates to
Checklist
hideTestRail: Results
Activity

shale99 August 3, 2017 at 11:34 AMEdited
pull request Folio 592
mod-circ-storage - temporarily depending on rmb 13.1.0-snapshot - will release rmb today and update pom

shale99 August 2, 2017 at 5:37 PM
right now it is ignored and replaced by the server side generated info every time - meaning the client does not need to send it, but if the client does, the section will be ignored but the request will not fail. Not sure we closed this issue - ignoring gives a bit more flexibility as it does not require the client to parse out sections of the json before sending (for example an update) - and if the info is included, the request wont fail it will just be ignored. this appriach gives a bit more flexibility but may be a bit less clean.

Marc Johnson August 2, 2017 at 4:29 PM
What have we decided to do for state altering requests that have the metadata section present?
Either:
Ignore the metadata property entirely, wholly replacing it with server derived state
Reject the request citing that clients should not provide the metadata property

David Crossley August 2, 2017 at 7:14 AM
That cleanup idea is .
In general, yes the shared schema area. In particular, when any schema has $ref with dot-dots, then there will be temp remnants. Any more than one set of dot-dots will be broken.

shale99 August 2, 2017 at 6:03 AM
, - i have merged this as it was a blocker for me to continue with the implementation. As discussed, David will be opening an issue on rmb , to delete /tmp schemas after the pojo generation step
Consider returning this information in form of HTTP headers and include for any entity stored in FOLIO.