-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Order placed without calling --submit-order #9
Comments
Hi there, that is intended behaviour (see the help text below).
|
OK. Thank you.
Chris Jackson
…On Mon, Jul 3, 2023 at 7:33 PM Mike Brady ***@***.***> wrote:
Hi there, that is intended behaviour (see the help text below).
--submit-order should be used when defining a full query instead of
passing a given granule's recordid. The purpose of the --record-id and
--record-ids arguments is a kind of shortcut for when I already knew the
granules so just needed to skip right to ordering.
--record-id INTEGER Specific Record Id to order from the desired
collection
--record-ids PATH File of line-separated Record Ids to order
from the desired collection
--order-id INTEGER Specific Order Id to download from EODMS
--order-ids PATH File of line-separated Order Ids to download
from EODMS
—
Reply to this email directly, view it on GitHub
<#9 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASCCH64JQ5HRCJCXBHPES33XONJETANCNFSM6AAAAAAZ43LKHM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
--
*Global Science and Technology, Inc*
*Consultant*
Global Ocean Associates
NCWCP E/RA3 Rm. 3217
5830 University Research Ct
College Park, MD 20740-3818
(301) 683-3315
|
Hi Chris I'm going to close this, but if you have a use-case for passing |
When ordering with the --record-id option (only) the order was placed without having set the --submit-order option.
e.g. eodms -c RCM --record-id 6887647
The text was updated successfully, but these errors were encountered: