From cdc9a27f2945b19920883079891e5ee536c69cfc Mon Sep 17 00:00:00 2001 From: Steven Mortimer Date: Tue, 27 Mar 2018 00:25:09 -0400 Subject: [PATCH] Updated Dates in README --- .travis.yml | 3 +-- README.Rmd | 20 ++++++++++---------- README.md | 20 ++++++++++---------- 3 files changed, 21 insertions(+), 22 deletions(-) diff --git a/.travis.yml b/.travis.yml index 9489c5a..000d4c6 100644 --- a/.travis.yml +++ b/.travis.yml @@ -1,6 +1,5 @@ before_install: -- openssl aes-256-cbc -K $encrypted_9568539fc584_key -iv $encrypted_9568539fc584_iv - -in tests/testthat/setup.tar.enc -out tests/testthat/setup.tar -d +- openssl aes-256-cbc -K $encrypted_9568539fc584_key -iv $encrypted_9568539fc584_iv -in tests/testthat/setup.tar.enc -out tests/testthat/setup.tar -d - tar xvf tests/testthat/setup.tar -C tests/testthat - R -q -e 'install.packages(c("remotes", "curl")); remotes::install_github("ropenscilabs/tic"); tic::prepare_all_stages(); tic::before_install()' diff --git a/README.Rmd b/README.Rmd index c052dff..e7af2ec 100644 --- a/README.Rmd +++ b/README.Rmd @@ -278,12 +278,12 @@ request_data <- list('filterStatement'=list('query'="WHERE name = 'TestCompany1' dfp_getCompaniesByStatement_result <- dfp_getCompaniesByStatement(request_data) request_data <- list(list(name=paste0('TestOrder'), - startDateTime=list(date=list(year=2017, month=12, day=1), + startDateTime=list(date=list(year=2018, month=12, day=1), hour=0, minute=0, second=0, timeZoneID='America/New_York'), - endDateTime=list(date=list(year=2017, month=12, day=31), + endDateTime=list(date=list(year=2018, month=12, day=31), hour=23, minute=59, second=59, @@ -301,7 +301,7 @@ dfp_createOrders_result <- dfp_createOrders(request_data) Below is an example of how to get objects by Publishers Query Language (PQL) statement. The statement is constructed as a list of lists that are nested to emulate the hierarchy of the XML to be created. The example uses the `dfp_getLineItemsByStatement` -function from the [LineItemService] (https://developers.google.com/doubleclick-publishers/docs/reference/v201702/LineItemService) +function from the [LineItemService] (https://developers.google.com/doubleclick-publishers/docs/reference/v201802/LineItemService) ```{r eval = FALSE} @@ -330,13 +330,13 @@ Below is an example of how to make a simple report request. # Documentation for the reportQuery object can be found in R using # ?dfp_ReportService_object_factory and searching for ReportQuery # Also online documentation is available that lists available child elements for reportQuery -# https://developers.google.com/doubleclick-publishers/docs/reference/v201702/ReportService.ReportQuery +# https://developers.google.com/doubleclick-publishers/docs/reference/v201802/ReportService.ReportQuery request_data <- list(reportJob=list(reportQuery=list(dimensions='MONTH_AND_YEAR', dimensions='AD_UNIT_ID', adUnitView='FLAT', columns='TOTAL_INVENTORY_LEVEL_IMPRESSIONS', - startDate=list(year=2015, month=10, day=1), - endDate=list(year=2015, month=10, day=31), + startDate=list(year=2018, month=10, day=1), + endDate=list(year=2018, month=10, day=31), dateRangeType='CUSTOM_DATE' ))) @@ -349,7 +349,7 @@ head(report_data) #### A More Detailed Explanation of the Report Process -Reports actually require 3 steps from the [ReportService] (https://developers.google.com/doubleclick-publishers/docs/reference/v201702/ReportService): +Reports actually require 3 steps from the [ReportService] (https://developers.google.com/doubleclick-publishers/docs/reference/v201802/ReportService): 1) to request the report, 2) check on its status, and 3) download. This basic process flow is required for all reports requested via this service. The wrapper function used above named `dfp_full_report_wrapper` manages all aspects of reporting, so this level of @@ -362,13 +362,13 @@ detail is not needed unless the wrapper service does not quite fit your needs. # Documentation for the reportQuery object can be found in R using # ?dfp_ReportService_object_factory and searching for ReportQuery # Also online documentation is available that lists available child elements for reportQuery -# https://developers.google.com/doubleclick-publishers/docs/reference/v201702/ReportService.ReportQuery +# https://developers.google.com/doubleclick-publishers/docs/reference/v201802/ReportService.ReportQuery request_data <- list(reportJob=list(reportQuery=list(dimensions='MONTH_AND_YEAR', dimensions='AD_UNIT_ID', adUnitView='FLAT', columns='TOTAL_INVENTORY_LEVEL_IMPRESSIONS', - startDate=list(year=2015, month=10, day=1), - endDate=list(year=2015, month=10, day=31), + startDate=list(year=2018, month=10, day=1), + endDate=list(year=2018, month=10, day=31), dateRangeType='CUSTOM_DATE' ))) diff --git a/README.md b/README.md index 8034164..ee02711 100644 --- a/README.md +++ b/README.md @@ -229,12 +229,12 @@ request_data <- list('filterStatement'=list('query'="WHERE name = 'TestCompany1' dfp_getCompaniesByStatement_result <- dfp_getCompaniesByStatement(request_data) request_data <- list(list(name=paste0('TestOrder'), - startDateTime=list(date=list(year=2017, month=12, day=1), + startDateTime=list(date=list(year=2018, month=12, day=1), hour=0, minute=0, second=0, timeZoneID='America/New_York'), - endDateTime=list(date=list(year=2017, month=12, day=31), + endDateTime=list(date=list(year=2018, month=12, day=31), hour=23, minute=59, second=59, @@ -248,7 +248,7 @@ dfp_createOrders_result <- dfp_createOrders(request_data) #### Get Line Items By A Filter -Below is an example of how to get objects by Publishers Query Language (PQL) statement. The statement is constructed as a list of lists that are nested to emulate the hierarchy of the XML to be created. The example uses the `dfp_getLineItemsByStatement` function from the \[LineItemService\] () +Below is an example of how to get objects by Publishers Query Language (PQL) statement. The statement is constructed as a list of lists that are nested to emulate the hierarchy of the XML to be created. The example uses the `dfp_getLineItemsByStatement` function from the \[LineItemService\] () ``` r @@ -276,13 +276,13 @@ Below is an example of how to make a simple report request. # Documentation for the reportQuery object can be found in R using # ?dfp_ReportService_object_factory and searching for ReportQuery # Also online documentation is available that lists available child elements for reportQuery -# https://developers.google.com/doubleclick-publishers/docs/reference/v201702/ReportService.ReportQuery +# https://developers.google.com/doubleclick-publishers/docs/reference/v201802/ReportService.ReportQuery request_data <- list(reportJob=list(reportQuery=list(dimensions='MONTH_AND_YEAR', dimensions='AD_UNIT_ID', adUnitView='FLAT', columns='TOTAL_INVENTORY_LEVEL_IMPRESSIONS', - startDate=list(year=2015, month=10, day=1), - endDate=list(year=2015, month=10, day=31), + startDate=list(year=2018, month=10, day=1), + endDate=list(year=2018, month=10, day=31), dateRangeType='CUSTOM_DATE' ))) @@ -295,7 +295,7 @@ head(report_data) #### A More Detailed Explanation of the Report Process -Reports actually require 3 steps from the \[ReportService\] (): 1) to request the report, 2) check on its status, and 3) download. This basic process flow is required for all reports requested via this service. The wrapper function used above named `dfp_full_report_wrapper` manages all aspects of reporting, so this level of detail is not needed unless the wrapper service does not quite fit your needs. +Reports actually require 3 steps from the \[ReportService\] (): 1) to request the report, 2) check on its status, and 3) download. This basic process flow is required for all reports requested via this service. The wrapper function used above named `dfp_full_report_wrapper` manages all aspects of reporting, so this level of detail is not needed unless the wrapper service does not quite fit your needs. ``` r @@ -304,13 +304,13 @@ Reports actually require 3 steps from the \[ReportService\] (