| Title | Order Management |
|---|---|
| URI | https://zenodo.org/record/8375323 (final version) |
| Revised version links | |
| Link to Metadata | |
| Date Issued to EIAC | 12.09.2023 |
| Submitted by | Agnieszka Pułapa |
| Outcome of EIAC review | endorsed online, 22.09.23 |
| Date Issued to EIAB | 22.09.23 |
| Outcome of EIAB review | 29.09.23 |
| On portal? | yes |
Overview
The proposed document has been submitted for inclusion in the EOSC Interoperability Framework.
Comments should be made either on eiac@eoscfuture.eu, where they will be archived for future reference or added to the change log below. Comments posted to other discussion methods will not be included in the review.
Statements of Support/Deny
All members of the EIAC are encouraged to make a statement of support or dissension in consideration of this proposal.
Name | Organisation | Support or Deny | Reason (if denied) |
|---|---|---|---|
| Thanassis Mantes | ATHENA RC | SUPPORT | |
| John Shepherdson | CESSDA ERIC | SUPPORT | |
| Sabeel Shah | Bielefeld University | Support | |
Comment/Change Log
Please fill in any comments or proposed changes below or add them as issues on the Github repository.
Number | Current Text | Proposed Text / Query | Commenter | Action |
|---|---|---|---|---|
| 1 | Various locations | Typos, as marked | John Shepherdson | Resolved |
| 2 | All figures in the document | Putting numbers to the figures' label will help in refering to them. Secondly, creating table of figures is recommended. | Sabeel Shah | Resolved |
| 3 | Page 2: Table of Tables | The first entry in this table refers to non-existing item. Secondly, few table in the document are missing numbering and are absent from Table of Tables. | Sabeel Shah | Resolved |
| 4 | Page 4: Description and main features | Definition or description of the term "offering" would make things more clear regarding functionality | Resolved | |
| 5 | Page 4: Description and main features | Same as above: A short description of the ordering process or flow would help providers. What is an order, how does it work related to resources? | Definition of ordering - done. An example will be provided in the last section together with specifying offer. | |
| 6 | Page 4: Description and main features | "Both are represented as a single resource type in the API: the Project Item". Reference, example? | Example provided. | |
| 7 | Page 6: Request and response format | Example or link with request/.response json? | Link provided. | |
| 8 | Page 8: EOSC Portal Operations Team | Is this the EPOT (EOSC Portal Onboarding Team)? Add to acronyms | No, it is not the same. Necessary clarification provided. | |
| 9 | Page 7: Definitions | This part seems somewhat 'generic' on the subject it tries to 'define' | I've made some changes but I think that definition should be rather generic. | |
| 10 | Page 9: | 'But any integrator can develop its own compatibility layer with their current ticketing system'. Is this described somewhere? | Link with the detailed information provided. | |
| 11 | Page 6: Trigger | curl or example for trigger call? | Done. | |
| 12 | Page 8-9: Interoperability Guidelines, (and general comment) | From a providers' view, I'm missing a clear '1-2-3 steps' instruction set on how I can:
APIs are there (maybe some more references needed in the text) but I'm not sure if it's clear how to use it. | Done. |