Document Location headers for created REST resources

[pratyushsinghal7]

References

• Related to create eperson via REST API endpoint /api/eperson/epersons: add Location header with eperson UUID in HTTP response DSpace#8881
• Companion to Add Location header to created REST resources DSpace#12848

Description

Document that successful JSON collection-resource creation returns 201 Created with an absolute Location header for the created resource.

The EPerson creation contract now includes the concrete canonical URI shape returned by POST /api/eperson/epersons.

Validation

• git diff --check
• Verified the documented EPerson URI matches the backend integration assertion in Add Location header to created REST resources DSpace#12848.

[pratyushsinghal7]

@saschaszott the review feedback has been addressed in 3e89c41 — the repository-wide 201/Location contract is now in README.md, and all three EPerson POST variants in epersons.md document the returned Location URI. The companion code PR DSpace/DSpace#12848 already has two approvals (yours and @MMilosz's) and is only waiting on this contract PR, so a re-review here would be much appreciated. Thanks!

[saschaszott]

@pratyushsinghal7 , I am not sure whether my concern has been addressed. Your change to the RestResourceController base class affects not only the creation of new EPersons via POST, but ultimately all DSOs created through postJsonInternal. My point was therefore whether this change should also be documented elsewhere in the RestContract (specifically, that the Location header contains the URI of the created resource).