Struct google_genomics1::AnnotationMethods

pub struct AnnotationMethods<'a, C, A> where
    C: 'a,
    A: 'a,  { /* fields omitted */ }

A builder providing access to all methods supported on annotation resources. It is not used directly, but through the Genomics hub.

Example

Instantiate a resource builder

extern crate hyper;
extern crate hyper_rustls;
extern crate yup_oauth2 as oauth2;
extern crate google_genomics1 as genomics1;
 
use std::default::Default;
use oauth2::{Authenticator, DefaultAuthenticatorDelegate, ApplicationSecret, MemoryStorage};
use genomics1::Genomics;
 
let secret: ApplicationSecret = Default::default();
let auth = Authenticator::new(&secret, DefaultAuthenticatorDelegate,
                              hyper::Client::with_connector(hyper::net::HttpsConnector::new(hyper_rustls::TlsClient::new())),
                              <MemoryStorage as Default>::default(), None);
let mut hub = Genomics::new(hyper::Client::with_connector(hyper::net::HttpsConnector::new(hyper_rustls::TlsClient::new())), auth);
// Usually you wouldn't bind this to a variable, but keep calling *CallBuilders*
// like `batch_create(...)`, `create(...)`, `delete(...)`, `get(...)`, `search(...)` and `update(...)`
// to build up your call.
let rb = hub.annotations();

Methods

impl<'a, C, A> AnnotationMethods<'a, C, A>

pub fn update(     &self,     request: Annotation,     annotation_id: &str ) -> AnnotationUpdateCall<'a, C, A>

Create a builder to help you perform the following task:

Updates an annotation. Caller must have WRITE permission for the associated dataset.

Arguments

• request - No description provided.
• annotationId - The ID of the annotation to be updated.

pub fn get(&self, annotation_id: &str) -> AnnotationGetCall<'a, C, A>

Create a builder to help you perform the following task:

Gets an annotation. Caller must have READ permission for the associated annotation set.

Arguments

• annotationId - The ID of the annotation to be retrieved.

pub fn search(     &self,     request: SearchAnnotationsRequest ) -> AnnotationSearchCall<'a, C, A>

Create a builder to help you perform the following task:

Searches for annotations that match the given criteria. Results are ordered by genomic coordinate (by reference sequence, then position). Annotations with equivalent genomic coordinates are returned in an unspecified order. This order is consistent, such that two queries for the same content (regardless of page size) yield annotations in the same order across their respective streams of paginated responses. Caller must have READ permission for the queried annotation sets.

Arguments

• request - No description provided.

pub fn delete(&self, annotation_id: &str) -> AnnotationDeleteCall<'a, C, A>

Create a builder to help you perform the following task:

Deletes an annotation. Caller must have WRITE permission for the associated annotation set.

Arguments

• annotationId - The ID of the annotation to be deleted.

pub fn create(&self, request: Annotation) -> AnnotationCreateCall<'a, C, A>

Create a builder to help you perform the following task:

Creates a new annotation. Caller must have WRITE permission for the associated annotation set.

The following fields are required:

• annotationSetId
• referenceName or referenceId

Transcripts

For annotations of type TRANSCRIPT, the following fields of transcript must be provided:

• exons.start
• exons.end

All other fields may be optionally specified, unless documented as being server-generated (for example, the id field). The annotated range must be no longer than 100Mbp (mega base pairs). See the Annotation resource for additional restrictions on each field.

Arguments

• request - No description provided.

pub fn batch_create(     &self,     request: BatchCreateAnnotationsRequest ) -> AnnotationBatchCreateCall<'a, C, A>

Create a builder to help you perform the following task:

Creates one or more new annotations atomically. All annotations must belong to the same annotation set. Caller must have WRITE permission for this annotation set. For optimal performance, batch positionally adjacent annotations together.

If the request has a systemic issue, such as an attempt to write to an inaccessible annotation set, the entire RPC will fail accordingly. For lesser data issues, when possible an error will be isolated to the corresponding batch entry in the response; the remaining well formed annotations will be created normally.

For details on the requirements for each individual annotation resource, see CreateAnnotation.

Arguments

• request - No description provided.

Trait Implementations

impl<'a, C, A> MethodsBuilder for AnnotationMethods<'a, C, A>