text:
<!---
 File generated by help_docs.sh. DO NOT EDIT.
 Please make changes to preamble and postscript wrappers as appropriate.
 --->

# peer lifecycle chaincode

The `peer lifecycle chaincode` subcommand allows administrators to use the
Fabric chaincode lifecycle to package a chaincode, install it on your peers,
approve a chaincode definition for your organization, and then commit the
definition to a channel. The chaincode is ready to be used after the definition
has been successfully committed to the channel. For more information, visit
[Fabric chaincode lifecycle](../chaincode_lifecycle.html).

*Note: These instructions use the Fabric chaincode lifecycle introduced in the
v2.0 release. If you would like to use the old lifecycle to install and
instantiate a chaincode, visit the [peer chaincode](peerchaincode.html) command
reference.*

## Syntax

The `peer lifecycle chaincode` command has the following subcommands:

  * package
  * install
  * queryinstalled
  * getinstalledpackage
  * calculatepackageid
  * approveformyorg
  * queryapproved
  * checkcommitreadiness
  * commit
  * querycommitted

Each peer lifecycle chaincode subcommand is described together with its options in its own
section in this topic.

## peer lifecycle
```
Perform _lifecycle operations

Usage:
  peer lifecycle [command]

Available Commands:
  chaincode   Perform chaincode operations: package|install|queryinstalled|getinstalledpackage|calculatepackageid|approveformyorg|queryapproved|checkcommitreadiness|commit|querycommitted

Flags:
  -h, --help   help for lifecycle

Use "peer lifecycle [command] --help" for more information about a command.
```

## peer lifecycle chaincode
```
Perform chaincode operations: package|install|queryinstalled|getinstalledpackage|calculatepackageid|approveformyorg|queryapproved|checkcommitreadiness|commit|querycommitted

Usage:
  peer lifecycle chaincode [command]

Available Commands:
  approveformyorg      Approve the chaincode definition for my org.
  calculatepackageid   Calculate the package ID for a chaincode.
  checkcommitreadiness Check whether a chaincode definition is ready to be committed on a channel.
  commit               Commit the chaincode definition on the channel.
  getinstalledpackage  Get an installed chaincode package from a peer.
  install              Install a chaincode.
  package              Package a chaincode
  queryapproved        Query an org's approved chaincode definition from its peer.
  querycommitted       Query the committed chaincode definitions by channel on a peer.
  queryinstalled       Query the installed chaincodes on a peer.

Flags:
      --cafile string                       Path to file containing PEM-encoded trusted certificate(s) for the ordering endpoint
      --certfile string                     Path to file containing PEM-encoded X509 public key to use for mutual TLS communication with the orderer endpoint
      --clientauth                          Use mutual TLS when communicating with the orderer endpoint
      --connTimeout duration                Timeout for client to connect (default 3s)
  -h, --help                                help for chaincode
      --keyfile string                      Path to file containing PEM-encoded private key to use for mutual TLS communication with the orderer endpoint
  -o, --orderer string                      Ordering service endpoint
      --ordererTLSHostnameOverride string   The hostname override to use when validating the TLS connection to the orderer
      --tls                                 Use TLS when communicating with the orderer endpoint
      --tlsHandshakeTimeShift duration      The amount of time to shift backwards for certificate expiration checks during TLS handshakes with the orderer endpoint

Use "peer lifecycle chaincode [command] --help" for more information about a command.
```

## peer lifecycle chaincode package
```
Package a chaincode and write the package to a file.

Usage:
  peer lifecycle chaincode package [outputfile] [flags]

Flags:
      --connectionProfile string       The fully qualified path to the connection profile that provides the necessary connection information for the network. Note: currently only supported for providing peer connection information
  -h, --help                           help for package
      --label string                   The package label contains a human-readable description of the package
  -l, --lang string                    Language the chaincode is written in (default "golang")
  -p, --path string                    Path to the chaincode
      --peerAddresses stringArray      The addresses of the peers to connect to
      --tlsRootCertFiles stringArray   If TLS is enabled, the paths to the TLS root cert files of the peers to connect to. The order and number of certs specified should match the --peerAddresses flag

Global Flags:
      --cafile string                       Path to file containing PEM-encoded trusted certificate(s) for the ordering endpoint
      --certfile string                     Path to file containing PEM-encoded X509 public key to use for mutual TLS communication with the orderer endpoint
      --clientauth                          Use mutual TLS when communicating with the orderer endpoint
      --connTimeout duration                Timeout for client to connect (default 3s)
      --keyfile string                      Path to file containing PEM-encoded private key to use for mutual TLS communication with the orderer endpoint
  -o, --orderer string                      Ordering service endpoint
      --ordererTLSHostnameOverride string   The hostname override to use when validating the TLS connection to the orderer
      --tls                                 Use TLS when communicating with the orderer endpoint
      --tlsHandshakeTimeShift duration      The amount of time to shift backwards for certificate expiration checks during TLS handshakes with the orderer endpoint
```

## peer lifecycle chaincode install
```
Install a chaincode on a peer.

Usage:
  peer lifecycle chaincode install [flags]

Flags:
      --connectionProfile string       The fully qualified path to the connection profile that provides the necessary connection information for the network. Note: currently only supported for providing peer connection information
  -h, --help                           help for install
      --peerAddresses stringArray      The addresses of the peers to connect to
      --targetPeer string              When using a connection profile, the name of the peer to target for this action
      --tlsRootCertFiles stringArray   If TLS is enabled, the paths to the TLS root cert files of the peers to connect to. The order and number of certs specified should match the --peerAddresses flag

Global Flags:
      --cafile string                       Path to file containing PEM-encoded trusted certificate(s) for the ordering endpoint
      --certfile string                     Path to file containing PEM-encoded X509 public key to use for mutual TLS communication with the orderer endpoint
      --clientauth                          Use mutual TLS when communicating with the orderer endpoint
      --connTimeout duration                Timeout for client to connect (default 3s)
      --keyfile string                      Path to file containing PEM-encoded private key to use for mutual TLS communication with the orderer endpoint
  -o, --orderer string                      Ordering service endpoint
      --ordererTLSHostnameOverride string   The hostname override to use when validating the TLS connection to the orderer
      --tls                                 Use TLS when communicating with the orderer endpoint
      --tlsHandshakeTimeShift duration      The amount of time to shift backwards for certificate expiration checks during TLS handshakes with the orderer endpoint
```

## peer lifecycle chaincode queryinstalled
```
Query the installed chaincodes on a peer.

Usage:
  peer lifecycle chaincode queryinstalled [flags]

Flags:
      --connectionProfile string       The fully qualified path to the connection profile that provides the necessary connection information for the network. Note: currently only supported for providing peer connection information
  -h, --help                           help for queryinstalled
  -O, --output string                  The output format for query results. Default is human-readable plain-text. json is currently the only supported format.
      --peerAddresses stringArray      The addresses of the peers to connect to
      --targetPeer string              When using a connection profile, the name of the peer to target for this action
      --tlsRootCertFiles stringArray   If TLS is enabled, the paths to the TLS root cert files of the peers to connect to. The order and number of certs specified should match the --peerAddresses flag

Global Flags:
      --cafile string                       Path to file containing PEM-encoded trusted certificate(s) for the ordering endpoint
      --certfile string                     Path to file containing PEM-encoded X509 public key to use for mutual TLS communication with the orderer endpoint
      --clientauth                          Use mutual TLS when communicating with the orderer endpoint
      --connTimeout duration                Timeout for client to connect (default 3s)
      --keyfile string                      Path to file containing PEM-encoded private key to use for mutual TLS communication with the orderer endpoint
  -o, --orderer string                      Ordering service endpoint
      --ordererTLSHostnameOverride string   The hostname override to use when validating the TLS connection to the orderer
      --tls                                 Use TLS when communicating with the orderer endpoint
      --tlsHandshakeTimeShift duration      The amount of time to shift backwards for certificate expiration checks during TLS handshakes with the orderer endpoint
```

## peer lifecycle chaincode getinstalledpackage
```
Get an installed chaincode package from a peer.

Usage:
  peer lifecycle chaincode getinstalledpackage [outputfile] [flags]

Flags:
      --connectionProfile string       The fully qualified path to the connection profile that provides the necessary connection information for the network. Note: currently only supported for providing peer connection information
  -h, --help                           help for getinstalledpackage
      --output-directory string        The output directory to use when writing a chaincode install package to disk. Default is the current working directory.
      --package-id string              The identifier of the chaincode install package
      --peerAddresses stringArray      The addresses of the peers to connect to
      --targetPeer string              When using a connection profile, the name of the peer to target for this action
      --tlsRootCertFiles stringArray   If TLS is enabled, the paths to the TLS root cert files of the peers to connect to. The order and number of certs specified should match the --peerAddresses flag

Global Flags:
      --cafile string                       Path to file containing PEM-encoded trusted certificate(s) for the ordering endpoint
      --certfile string                     Path to file containing PEM-encoded X509 public key to use for mutual TLS communication with the orderer endpoint
      --clientauth                          Use mutual TLS when communicating with the orderer endpoint
      --connTimeout duration                Timeout for client to connect (default 3s)
      --keyfile string                      Path to file containing PEM-encoded private key to use for mutual TLS communication with the orderer endpoint
  -o, --orderer string                      Ordering service endpoint
      --ordererTLSHostnameOverride string   The hostname override to use when validating the TLS connection to the orderer
      --tls                                 Use TLS when communicating with the orderer endpoint
      --tlsHandshakeTimeShift duration      The amount of time to shift backwards for certificate expiration checks during TLS handshakes with the orderer endpoint
```

## peer lifecycle chaincode calculatepackageid
```
Calculate the package ID for a packaged chaincode.

Usage:
  peer lifecycle chaincode calculatepackageid packageFile [flags]

Flags:
      --connectionProfile string       The fully qualified path to the connection profile that provides the necessary connection information for the network. Note: currently only supported for providing peer connection information
  -h, --help                           help for calculatepackageid
  -O, --output string                  The output format for query results. Default is human-readable plain-text. json is currently the only supported format.
      --peerAddresses stringArray      The addresses of the peers to connect to
      --tlsRootCertFiles stringArray   If TLS is enabled, the paths to the TLS root cert files of the peers to connect to. The order and number of certs specified should match the --peerAddresses flag

Global Flags:
      --cafile string                       Path to file containing PEM-encoded trusted certificate(s) for the ordering endpoint
      --certfile string                     Path to file containing PEM-encoded X509 public key to use for mutual TLS communication with the orderer endpoint
      --clientauth                          Use mutual TLS when communicating with the orderer endpoint
      --connTimeout duration                Timeout for client to connect (default 3s)
      --keyfile string                      Path to file containing PEM-encoded private key to use for mutual TLS communication with the orderer endpoint
  -o, --orderer string                      Ordering service endpoint
      --ordererTLSHostnameOverride string   The hostname override to use when validating the TLS connection to the orderer
      --tls                                 Use TLS when communicating with the orderer endpoint
      --tlsHandshakeTimeShift duration      The amount of time to shift backwards for certificate expiration checks during TLS handshakes with the orderer endpoint
```

## peer lifecycle chaincode approveformyorg
```
Approve the chaincode definition for my organization.

Usage:
  peer lifecycle chaincode approveformyorg [flags]

Flags:
      --channel-config-policy string   The endorsement policy associated to this chaincode specified as a channel config policy reference
  -C, --channelID string               The channel on which this command should be executed
      --collections-config string      The fully qualified path to the collection JSON file including the file name
      --connectionProfile string       The fully qualified path to the connection profile that provides the necessary connection information for the network. Note: currently only supported for providing peer connection information
  -E, --endorsement-plugin string      The name of the endorsement plugin to be used for this chaincode
  -h, --help                           help for approveformyorg
      --init-required                  Whether the chaincode requires invoking 'init'
  -n, --name string                    Name of the chaincode
      --package-id string              The identifier of the chaincode install package
      --peerAddresses stringArray      The addresses of the peers to connect to
      --sequence int                   The sequence number of the chaincode definition for the channel
      --signature-policy string        The endorsement policy associated to this chaincode specified as a signature policy
      --tlsRootCertFiles stringArray   If TLS is enabled, the paths to the TLS root cert files of the peers to connect to. The order and number of certs specified should match the --peerAddresses flag
  -V, --validation-plugin string       The name of the validation plugin to be used for this chaincode
  -v, --version string                 Version of the chaincode
      --waitForEvent                   Whether to wait for the event from each peer's deliver filtered service signifying that the transaction has been committed successfully (default true)
      --waitForEventTimeout duration   Time to wait for the event from each peer's deliver filtered service signifying that the 'invoke' transaction has been committed successfully (default 30s)

Global Flags:
      --cafile string                       Path to file containing PEM-encoded trusted certificate(s) for the ordering endpoint
      --certfile string                     Path to file containing PEM-encoded X509 public key to use for mutual TLS communication with the orderer endpoint
      --clientauth                          Use mutual TLS when communicating with the orderer endpoint
      --connTimeout duration                Timeout for client to connect (default 3s)
      --keyfile string                      Path to file containing PEM-encoded private key to use for mutual TLS communication with the orderer endpoint
  -o, --orderer string                      Ordering service endpoint
      --ordererTLSHostnameOverride string   The hostname override to use when validating the TLS connection to the orderer
      --tls                                 Use TLS when communicating with the orderer endpoint
      --tlsHandshakeTimeShift duration      The amount of time to shift backwards for certificate expiration checks during TLS handshakes with the orderer endpoint
```

## peer lifecycle chaincode queryapproved
```
Query an organization's approved chaincode definition from its peer.

Usage:
  peer lifecycle chaincode queryapproved [flags]

Flags:
  -C, --channelID string               The channel on which this command should be executed
      --connectionProfile string       The fully qualified path to the connection profile that provides the necessary connection information for the network. Note: currently only supported for providing peer connection information
  -h, --help                           help for queryapproved
  -n, --name string                    Name of the chaincode
  -O, --output string                  The output format for query results. Default is human-readable plain-text. json is currently the only supported format.
      --peerAddresses stringArray      The addresses of the peers to connect to
      --sequence int                   The sequence number of the chaincode definition for the channel
      --tlsRootCertFiles stringArray   If TLS is enabled, the paths to the TLS root cert files of the peers to connect to. The order and number of certs specified should match the --peerAddresses flag

Global Flags:
      --cafile string                       Path to file containing PEM-encoded trusted certificate(s) for the ordering endpoint
      --certfile string                     Path to file containing PEM-encoded X509 public key to use for mutual TLS communication with the orderer endpoint
      --clientauth                          Use mutual TLS when communicating with the orderer endpoint
      --connTimeout duration                Timeout for client to connect (default 3s)
      --keyfile string                      Path to file containing PEM-encoded private key to use for mutual TLS communication with the orderer endpoint
  -o, --orderer string                      Ordering service endpoint
      --ordererTLSHostnameOverride string   The hostname override to use when validating the TLS connection to the orderer
      --tls                                 Use TLS when communicating with the orderer endpoint
      --tlsHandshakeTimeShift duration      The amount of time to shift backwards for certificate expiration checks during TLS handshakes with the orderer endpoint
```

## peer lifecycle chaincode checkcommitreadiness
```
Check whether a chaincode definition is ready to be committed on a channel.

Usage:
  peer lifecycle chaincode checkcommitreadiness [flags]

Flags:
      --channel-config-policy string   The endorsement policy associated to this chaincode specified as a channel config policy reference
  -C, --channelID string               The channel on which this command should be executed
      --collections-config string      The fully qualified path to the collection JSON file including the file name
      --connectionProfile string       The fully qualified path to the connection profile that provides the necessary connection information for the network. Note: currently only supported for providing peer connection information
  -E, --endorsement-plugin string      The name of the endorsement plugin to be used for this chaincode
  -h, --help                           help for checkcommitreadiness
      --init-required                  Whether the chaincode requires invoking 'init'
  -n, --name string                    Name of the chaincode
  -O, --output string                  The output format for query results. Default is human-readable plain-text. json is currently the only supported format.
      --peerAddresses stringArray      The addresses of the peers to connect to
      --sequence int                   The sequence number of the chaincode definition for the channel
      --signature-policy string        The endorsement policy associated to this chaincode specified as a signature policy
      --tlsRootCertFiles stringArray   If TLS is enabled, the paths to the TLS root cert files of the peers to connect to. The order and number of certs specified should match the --peerAddresses flag
  -V, --validation-plugin string       The name of the validation plugin to be used for this chaincode
  -v, --version string                 Version of the chaincode

Global Flags:
      --cafile string                       Path to file containing PEM-encoded trusted certificate(s) for the ordering endpoint
      --certfile string                     Path to file containing PEM-encoded X509 public key to use for mutual TLS communication with the orderer endpoint
      --clientauth                          Use mutual TLS when communicating with the orderer endpoint
      --connTimeout duration                Timeout for client to connect (default 3s)
      --keyfile string                      Path to file containing PEM-encoded private key to use for mutual TLS communication with the orderer endpoint
  -o, --orderer string                      Ordering service endpoint
      --ordererTLSHostnameOverride string   The hostname override to use when validating the TLS connection to the orderer
      --tls                                 Use TLS when communicating with the orderer endpoint
      --tlsHandshakeTimeShift duration      The amount of time to shift backwards for certificate expiration checks during TLS handshakes with the orderer endpoint
```

## peer lifecycle chaincode commit
```
Commit the chaincode definition on the channel.

Usage:
  peer lifecycle chaincode commit [flags]

Flags:
      --channel-config-policy string   The endorsement policy associated to this chaincode specified as a channel config policy reference
  -C, --channelID string               The channel on which this command should be executed
      --collections-config string      The fully qualified path to the collection JSON file including the file name
      --connectionProfile string       The fully qualified path to the connection profile that provides the necessary connection information for the network. Note: currently only supported for providing peer connection information
  -E, --endorsement-plugin string      The name of the endorsement plugin to be used for this chaincode
  -h, --help                           help for commit
      --init-required                  Whether the chaincode requires invoking 'init'
  -n, --name string                    Name of the chaincode
      --peerAddresses stringArray      The addresses of the peers to connect to
      --sequence int                   The sequence number of the chaincode definition for the channel
      --signature-policy string        The endorsement policy associated to this chaincode specified as a signature policy
      --tlsRootCertFiles stringArray   If TLS is enabled, the paths to the TLS root cert files of the peers to connect to. The order and number of certs specified should match the --peerAddresses flag
  -V, --validation-plugin string       The name of the validation plugin to be used for this chaincode
  -v, --version string                 Version of the chaincode
      --waitForEvent                   Whether to wait for the event from each peer's deliver filtered service signifying that the transaction has been committed successfully (default true)
      --waitForEventTimeout duration   Time to wait for the event from each peer's deliver filtered service signifying that the 'invoke' transaction has been committed successfully (default 30s)

Global Flags:
      --cafile string                       Path to file containing PEM-encoded trusted certificate(s) for the ordering endpoint
      --certfile string                     Path to file containing PEM-encoded X509 public key to use for mutual TLS communication with the orderer endpoint
      --clientauth                          Use mutual TLS when communicating with the orderer endpoint
      --connTimeout duration                Timeout for client to connect (default 3s)
      --keyfile string                      Path to file containing PEM-encoded private key to use for mutual TLS communication with the orderer endpoint
  -o, --orderer string                      Ordering service endpoint
      --ordererTLSHostnameOverride string   The hostname override to use when validating the TLS connection to the orderer
      --tls                                 Use TLS when communicating with the orderer endpoint
      --tlsHandshakeTimeShift duration      The amount of time to shift backwards for certificate expiration checks during TLS handshakes with the orderer endpoint
```

## peer lifecycle chaincode querycommitted
```
Query the committed chaincode definitions by channel on a peer. Optional: provide a chaincode name to query a specific definition.

Usage:
  peer lifecycle chaincode querycommitted [flags]

Flags:
  -C, --channelID string               The channel on which this command should be executed
      --connectionProfile string       The fully qualified path to the connection profile that provides the necessary connection information for the network. Note: currently only supported for providing peer connection information
  -h, --help                           help for querycommitted
  -n, --name string                    Name of the chaincode
  -O, --output string                  The output format for query results. Default is human-readable plain-text. json is currently the only supported format.
      --peerAddresses stringArray      The addresses of the peers to connect to
      --tlsRootCertFiles stringArray   If TLS is enabled, the paths to the TLS root cert files of the peers to connect to. The order and number of certs specified should match the --peerAddresses flag

Global Flags:
      --cafile string                       Path to file containing PEM-encoded trusted certificate(s) for the ordering endpoint
      --certfile string                     Path to file containing PEM-encoded X509 public key to use for mutual TLS communication with the orderer endpoint
      --clientauth                          Use mutual TLS when communicating with the orderer endpoint
      --connTimeout duration                Timeout for client to connect (default 3s)
      --keyfile string                      Path to file containing PEM-encoded private key to use for mutual TLS communication with the orderer endpoint
  -o, --orderer string                      Ordering service endpoint
      --ordererTLSHostnameOverride string   The hostname override to use when validating the TLS connection to the orderer
      --tls                                 Use TLS when communicating with the orderer endpoint
      --tlsHandshakeTimeShift duration      The amount of time to shift backwards for certificate expiration checks during TLS handshakes with the orderer endpoint
```

## Example Usage

### peer lifecycle chaincode package example

A chaincode needs to be packaged before it can be installed on your peers.
This example uses the `peer lifecycle chaincode package` command to package
a Go chaincode.

  * Use the `--path` flag to indicate the location of the chaincode.
    The path must be a fully qualified path or a path relative to your present working directory.
  * Use the `--label` flag to provide a chaincode package label of `myccv1`
    that your organization will use to identify the package.

    ```
    peer lifecycle chaincode package mycc.tar.gz --path $CHAINCODE_DIR --lang golang --label myccv1
    ```

### peer lifecycle chaincode install example

After the chaincode is packaged, you can use the `peer chaincode install` command
to install the chaincode on your peers.

  * Install the `mycc.tar.gz ` package on `peer0.org1.example.com:7051` (the
    peer defined by `--peerAddresses`).

    ```
    peer lifecycle chaincode install mycc.tar.gz --peerAddresses peer0.org1.example.com:7051
    ```
    If successful, the command will return the package identifier. The
    package ID is the package label combined with a hash of the chaincode
    package taken by the peer.
    ```
    2019-03-13 13:48:53.691 UTC [cli.lifecycle.chaincode] submitInstallProposal -> INFO 001 Installed remotely: response:<status:200 payload:"\nEmycc:ebd89878c2bbccf62f68c36072626359376aa83c36435a058d453e8dbfd894cc" >
    2019-03-13 13:48:53.691 UTC [cli.lifecycle.chaincode] submitInstallProposal -> INFO 002 Chaincode code package identifier: mycc:a7ca45a7cc85f1d89c905b775920361ed089a364e12a9b6d55ba75c965ddd6a9
    ```

### peer lifecycle chaincode queryinstalled example

You need to use the chaincode package identifier to approve a chaincode
definition for your organization. You can find the package ID for the
chaincodes you have installed by using the
`peer lifecycle chaincode queryinstalled` command:

```
peer lifecycle chaincode queryinstalled --peerAddresses peer0.org1.example.com:7051
```

A successful command will return the package ID associated with the
package label.

```
Get installed chaincodes on peer:
Package ID: myccv1:a7ca45a7cc85f1d89c905b775920361ed089a364e12a9b6d55ba75c965ddd6a9, Label: myccv1
```

  * You can also use the `--output` flag to have the CLI format the output as
    JSON.

    ```
    peer lifecycle chaincode queryinstalled --peerAddresses peer0.org1.example.com:7051 --output json
    ```

    If successful, the command will return the chaincodes you have installed as JSON.

    ```
    {
      "installed_chaincodes": [
        {
          "package_id": "mycc_1:aab9981fa5649cfe25369fce7bb5086a69672a631e4f95c4af1b5198fe9f845b",
          "label": "mycc_1",
          "references": {
            "mychannel": {
              "chaincodes": [
                {
                  "name": "mycc",
                  "version": "1"
                }
              ]
            }
          }
        }
      ]
    }
    ```

### peer lifecycle chaincode getinstalledpackage example

You can retrieve an installed chaincode package from a peer using the
`peer lifecycle chaincode getinstalledpackage` command. Use the package
identifier returned by `queryinstalled`.

  * Use the `--package-id` flag to pass in the chaincode package identifier. Use
  the `--output-directory` flag to specify where to write the chaincode package.
  If the output directory is not specified, the chaincode package will be written
  in the current directory.

  ```
  peer lifecycle chaincode getinstalledpackage --package-id myccv1:a7ca45a7cc85f1d89c905b775920361ed089a364e12a9b6d55ba75c965ddd6a9 --output-directory /tmp --peerAddresses peer0.org1.example.com:7051
  ```

### peer lifecycle chaincode calculatepackageid example

You can calculate the package ID from a packaged chaincode without installing the chaincode on peers
using the `peer lifecycle chaincode calculatepackageid` command.
This command will be useful, for example, in the following cases:

  * When multiple chaincode packages with the same label name are installed,
  it is possible to identify which ID corresponds to which package later.
  * To check whether a particular chaincode package is installed or not without
  installing that package.

Calcuate the package ID for the `mycc.tar.gz` package:

```
peer lifecycle chaincode calculatepackageid mycc.tar.gz
```

A successful command will return the package ID for the packaged chaincode.

```
myccv1:cc7bb5f50a53c207f68d37e9423c32f968083282e5ffac00d41ffc5768dc1873
```

  * You can also use the `--output` flag to have the CLI format the output as JSON.

    ```
    peer lifecycle chaincode calculatepackageid mycc.tar.gz --output json
    ```

    If successful, the command will return the chaincode package ID as JSON.

    ```
    {
      "package_id": "myccv1:cc7bb5f50a53c207f68d37e9423c32f968083282e5ffac00d41ffc5768dc1873"
    }
    ```

### peer lifecycle chaincode approveformyorg example

Once the chaincode package has been installed on your peers, you can approve
a chaincode definition for your organization. The chaincode definition includes
the important parameters of chaincode governance, including the chaincode name,
version and the endorsement policy.

Here is an example of the `peer lifecycle chaincode approveformyorg` command,
which approves the definition of a chaincode  named `mycc` at version `1.0` on
channel `mychannel`.

  * Use the `--package-id` flag to pass in the chaincode package identifier. Use
    the `--signature-policy` flag to define an endorsement policy for the chaincode.
    Use the `init-required` flag to request the execution of the `Init`
    function to initialize the chaincode.

    ```
    export ORDERER_CA=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

    peer lifecycle chaincode approveformyorg  -o orderer.example.com:7050 --tls --cafile $ORDERER_CA --channelID mychannel --name mycc --version 1.0 --init-required --package-id myccv1:a7ca45a7cc85f1d89c905b775920361ed089a364e12a9b6d55ba75c965ddd6a9 --sequence 1 --signature-policy "AND ('Org1MSP.peer','Org2MSP.peer')"

    2019-03-18 16:04:09.046 UTC [cli.lifecycle.chaincode] InitCmdFactory -> INFO 001 Retrieved channel (mychannel) orderer endpoint: orderer.example.com:7050
    2019-03-18 16:04:11.253 UTC [chaincodeCmd] ClientWait -> INFO 002 txid [efba188ca77889cc1c328fc98e0bb12d3ad0abcda3f84da3714471c7c1e6c13c] committed with status (VALID) at peer0.org1.example.com:7051
    ```

  * You can also use the `--channel-config-policy` flag use a policy inside
    the channel configuration as the chaincode endorsement policy. The default
    endorsement policy is `Channel/Application/Endorsement`

    ```
    export ORDERER_CA=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

    peer lifecycle chaincode approveformyorg -o orderer.example.com:7050 --tls --cafile $ORDERER_CA --channelID mychannel --name mycc --version 1.0 --init-required --package-id myccv1:a7ca45a7cc85f1d89c905b775920361ed089a364e12a9b6d55ba75c965ddd6a9 --sequence 1 --channel-config-policy Channel/Application/Admins

    2019-03-18 16:04:09.046 UTC [cli.lifecycle.chaincode] InitCmdFactory -> INFO 001 Retrieved channel (mychannel) orderer endpoint: orderer.example.com:7050
    2019-03-18 16:04:11.253 UTC [chaincodeCmd] ClientWait -> INFO 002 txid [efba188ca77889cc1c328fc98e0bb12d3ad0abcda3f84da3714471c7c1e6c13c] committed with status (VALID) at peer0.org1.example.com:7051
    ```

### peer lifecycle chaincode queryapproved example

You can query an organization's approved chaincode definition by using the `peer lifecycle chaincode queryapproved` command.
You can use this command to see the details (including package ID) of approved chaincode definitions.

  * Here is an example of the `peer lifecycle chaincode queryapproved` command,
    which queries the approved definition of a chaincode named `mycc` at sequence number `1` on
    channel `mychannel`.

    ```
    peer lifecycle chaincode queryapproved -C mychannel -n mycc --sequence 1

    Approved chaincode definition for chaincode 'mycc' on channel 'mychannel':
    sequence: 1, version: 1, init-required: true, package-id: mycc_1:d02f72000e7c0f715840f51cb8d72d70bc1ba230552f8445dded0ec8b6e0b830, endorsement plugin: escc, validation plugin: vscc
    ```

    If NO package is specified for the approved definition, this command will display an empty package ID.

  * You can also use this command without specifying the sequence number in order to query the latest approved definition (latest: the newer of the currently defined sequence number and the next sequence number).

    ```
    peer lifecycle chaincode queryapproved -C mychannel -n mycc

    Approved chaincode definition for chaincode 'mycc' on channel 'mychannel':
    sequence: 3, version: 3, init-required: false, package-id: mycc_1:d02f72000e7c0f715840f51cb8d72d70bc1ba230552f8445dded0ec8b6e0b830, endorsement plugin: escc, validation plugin: vscc
    ```

  * You can also use the `--output` flag to have the CLI format the output as
    JSON.

    - When querying an approved chaincode definition for which package is specified

      ```
      peer lifecycle chaincode queryapproved -C mychannel -n mycc --sequence 1 --output json
      ```

      If successful, the command will return a JSON that has the approved chaincode definition for chaincode `mycc` at sequence number `1` on channel `mychannel`.

      ```
      {
        "sequence": 1,
        "version": "1",
        "endorsement_plugin": "escc",
        "validation_plugin": "vscc",
        "validation_parameter": "EiAvQ2hhbm5lbC9BcHBsaWNhdGlvbi9FbmRvcnNlbWVudA==",
        "collections": {},
        "init_required": true,
        "source": {
          "Type": {
            "LocalPackage": {
              "package_id": "mycc_1:d02f72000e7c0f715840f51cb8d72d70bc1ba230552f8445dded0ec8b6e0b830"
            }
          }
        }
      }
      ```

    - When querying an approved chaincode definition for which package is NOT specified

      ```
      peer lifecycle chaincode queryapproved -C mychannel -n mycc --sequence 2 --output json
      ```

      If successful, the command will return a JSON that has the approved chaincode definition for chaincode `mycc` at sequence number `2` on channel `mychannel`.

      ```
      {
        "sequence": 2,
        "version": "2",
        "endorsement_plugin": "escc",
        "validation_plugin": "vscc",
        "validation_parameter": "EiAvQ2hhbm5lbC9BcHBsaWNhdGlvbi9FbmRvcnNlbWVudA==",
        "collections": {},
        "source": {
          "Type": {
            "Unavailable": {}
          }
        }
      }
      ```

### peer lifecycle chaincode checkcommitreadiness example

You can check whether a chaincode definition is ready to be committed using the
`peer lifecycle chaincode checkcommitreadiness` command, which will return
successfully if a subsequent commit of the definition is expected to succeed. It
also outputs which organizations have approved the chaincode definition. If an
organization has approved the chaincode definition specified in the command, the
command will return a value of true. You can use this command to learn whether enough
channel members have approved a chaincode definition to meet the
`/Channel/Application/Endorsement` policy (a majority by default) before the
definition can be committed to a channel.

  * Here is an example of the `peer lifecycle chaincode checkcommitreadiness` command,
    which checks a chaincode named `mycc` at version `1.0` on channel `mychannel`.

    ```
    export ORDERER_CA=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

    peer lifecycle chaincode checkcommitreadiness -o orderer.example.com:7050 --channelID mychannel --tls --cafile $ORDERER_CA --name mycc --version 1.0 --init-required --sequence 1
    ```

    If successful, the command will return the organizations that have approved
    the chaincode definition.

    ```
    Chaincode definition for chaincode 'mycc', version '1.0', sequence '1' on channel
    'mychannel' approval status by org:
    Org1MSP: true
    Org2MSP: true
    ```

  * You can also use the `--output` flag to have the CLI format the output as
    JSON.

    ```
    export ORDERER_CA=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

    peer lifecycle chaincode checkcommitreadiness -o orderer.example.com:7050 --channelID mychannel --tls --cafile $ORDERER_CA --name mycc --version 1.0 --init-required --sequence 1 --output json
    ```

    If successful, the command will return a JSON map that shows if an organization
    has approved the chaincode definition.

    ```
    {
       "Approvals": {
          "Org1MSP": true,
          "Org2MSP": true
       }
    }
    ```

### peer lifecycle chaincode commit example

Once a sufficient number of organizations approve a chaincode definition for
their organizations (a majority by default), one organization can commit the
definition the channel using the `peer lifecycle chaincode commit` command:

  * This command needs to target the peers of other organizations on the channel
    to collect their organization endorsement for the definition.

    ```
    export ORDERER_CA=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

    peer lifecycle chaincode commit -o orderer.example.com:7050 --channelID mychannel --name mycc --version 1.0 --sequence 1 --init-required --tls --cafile $ORDERER_CA --peerAddresses peer0.org1.example.com:7051 --peerAddresses peer0.org2.example.com:9051

    2019-03-18 16:14:27.258 UTC [chaincodeCmd] ClientWait -> INFO 001 txid [b6f657a14689b27d69a50f39590b3949906b5a426f9d7f0dcee557f775e17882] committed with status (VALID) at peer0.org2.example.com:9051
    2019-03-18 16:14:27.321 UTC [chaincodeCmd] ClientWait -> INFO 002 txid [b6f657a14689b27d69a50f39590b3949906b5a426f9d7f0dcee557f775e17882] committed with status (VALID) at peer0.org1.example.com:7051
    ```

### peer lifecycle chaincode querycommitted example

You can query the chaincode definitions that have been committed to a channel by
using the `peer lifecycle chaincode querycommitted` command. You can use this
command to query the current definition sequence number before upgrading a
chaincode.

  * You need to supply the chaincode name and channel name in order to query a
    specific chaincode definition and the organizations that have approved it.

    ```
    export ORDERER_CA=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

    peer lifecycle chaincode querycommitted -o orderer.example.com:7050 --channelID mychannel --name mycc --tls --cafile $ORDERER_CA --peerAddresses peer0.org1.example.com:7051

    Committed chaincode definition for chaincode 'mycc' on channel 'mychannel':
    Version: 1, Sequence: 1, Endorsement Plugin: escc, Validation Plugin: vscc
    Approvals: [Org1MSP: true, Org2MSP: true]
    ```

  * You can also specify just the channel name in order to query all chaincode
  definitions on that channel.

    ```
    export ORDERER_CA=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

    peer lifecycle chaincode querycommitted -o orderer.example.com:7050 --channelID mychannel --tls --cafile $ORDERER_CA --peerAddresses peer0.org1.example.com:7051

    Committed chaincode definitions on channel 'mychannel':
    Name: mycc, Version: 1, Sequence: 1, Endorsement Plugin: escc, Validation Plugin: vscc
    Name: yourcc, Version: 2, Sequence: 3, Endorsement Plugin: escc, Validation Plugin: vscc
    ```

  * You can also use the `--output` flag to have the CLI format the output as
    JSON.

    - For querying a specific chaincode definition

      ```
      export ORDERER_CA=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

      peer lifecycle chaincode querycommitted -o orderer.example.com:7050 --channelID mychannel --name mycc --tls --cafile $ORDERER_CA --peerAddresses peer0.org1.example.com:7051 --output json
      ```

      If successful, the command will return a JSON that has committed chaincode definition for chaincode 'mycc' on channel 'mychannel'.

      ```
      {
        "sequence": 1,
        "version": "1",
        "endorsement_plugin": "escc",
        "validation_plugin": "vscc",
        "validation_parameter": "EiAvQ2hhbm5lbC9BcHBsaWNhdGlvbi9FbmRvcnNlbWVudA==",
        "collections": {},
        "init_required": true,
        "approvals": {
          "Org1MSP": true,
          "Org2MSP": true
        }
      }
      ```

      The `validation_parameter` is base64 encoded. An example of the command to decode it is as follows.

      ```
      echo EiAvQ2hhbm5lbC9BcHBsaWNhdGlvbi9FbmRvcnNlbWVudA== | base64 -d

       /Channel/Application/Endorsement
      ```

    - For querying all chaincode definitions on that channel

      ```
      export ORDERER_CA=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

      peer lifecycle chaincode querycommitted -o orderer.example.com:7050 --channelID mychannel --tls --cafile $ORDERER_CA --peerAddresses peer0.org1.example.com:7051 --output json
      ```

      If successful, the command will return a JSON that has committed chaincode definitions on channel 'mychannel'.

      ```
      {
        "chaincode_definitions": [
          {
            "name": "mycc",
            "sequence": 1,
            "version": "1",
            "endorsement_plugin": "escc",
            "validation_plugin": "vscc",
            "validation_parameter": "EiAvQ2hhbm5lbC9BcHBsaWNhdGlvbi9FbmRvcnNlbWVudA==",
            "collections": {},
            "init_required": true
          },
          {
            "name": "yourcc",
            "sequence": 3,
            "version": "2",
            "endorsement_plugin": "escc",
            "validation_plugin": "vscc",
            "validation_parameter": "EiAvQ2hhbm5lbC9BcHBsaWNhdGlvbi9FbmRvcnNlbWVudA==",
            "collections": {}
          }
        ]
      }
      ```

<a rel="license" href="http://creativecommons.org/licenses/by/4.0/"><img alt="Creative Commons License" style="border-width:0" src="https://i.creativecommons.org/l/by/4.0/88x31.png" /></a><br />This work is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International License</a>.


With her black hair, red lips, and lily-white skin, Summer is as beautiful as her father's garden. And her life in the mountains of West Virginia seems like a fairy tale; her parents sing and dance with her, Cousin Nancy dotes on her, and she is about to get a new baby brother. But when the baby dies soon after he's born, taking Summer's mama with him, Summer's fairy-tale life turns grim. Things get even worse when her father marries a woman who brings poisons and magical mirrors into Summer's world. Stepmama puts up a pretty face, but Summer suspects she's up to no good - and is afraid she's powerless to stop her.
This Snow White tale filled with magic and intrigue during the early twentieth century in Appalachia will be hard to forget.
OOooh a Snow White retelling! I'm all for that. I don't think I've ever seen one set in early 20th century Appalachia either, so I'm really curious to see how the author adapts the story to this setting. And how can I say no to that gorgeous cover?
Let's see...historical setting, family secrets, a magical stone, a fabled map, murderous bushrangers, a handsome sailor, shipwrecks, adventure, a perilous quest...why would I not want to read it?! This just sounds like everything I love all wrapped up into one beautiful book. The sequel, The Eternal Sea (with a disappointingly meh cover) just came out earlier this month, so I should really get to reading this book already!
Great picks :) Snow in Summer's going on my TBR list. I've been wanting to read Everlasting for a while too- I really must try to get hold of it.
Thank you so much for changing to pop up comments for me until the problem's fixed. It's lovely of you and I really appreciate it!
Snow in Summer sounds just like my kind of book!
And I remember wanting to read Everlasting, though I don't know why I never made more of an effort for it:P still, I like the sound of it!
I haven't read either book but I've heard amazing things about Everlasting. I was sold on the cover a while ago, it looks amazing.
I haven't read these either. I've been wanting to read Everlasting. I've only read a few books by Jane Yolen. I've always meant to read more.
I love that there are so many new revisions of fairy tales coming out!
They both sound great!! I haven't heard of either of them but I'm very interested.
I didn't really like Everlasting but that was partly because I thought it was a straight historical and I was surprised to find a supernatural element. I also didn't like the love interest Oscar but I think he might be more to your taste.
In a way, I'd compare it to The Vespertine by Saundra Mitchell where I loved the historical elements but not the supernatural.
A Snow White retelling!!! YES! I love the illustrative cover, very artistic.
Everlasting sounds super fun! Gimme.
I totally still need to read Everlasting too!!
That cover IS gorgeous. Would love to read it too!
Snow in Summer looks beautiful! And in Appalachia. Sounds great!
Bookworm1858, Oh too bad! It really does turn me off from a book when I go in expecting one thing and end up getting something else. Hopefully I'll like Oscar more. I've been getting a bunch of love interests that just haven't been doing it for me lately.


text:
Terms: Theodolites
Terms: Potentiometers
Terms: Electricity
Terms: geology -- models
Terms: Levelling
Leeds & Northrup Company, Philadelphia (60)
Weston Electrical Instrument Corporation, Newark, NJ (18)
D. Appleton and Company, New York (7)
G. Masson, Éditeur, Paris (5)
Sherwood, Gilbert, and Piper, London (5)
E. & F. N. Spon, London (4)
Longmans, Green, and Co., London (4)
Burndy Library, Norwalk, CT (3)
John Murray, London (3)
Leeds & Northrup, Philadelphia (3)
The Leeds & Northrup Company, Philadelphia (3)
Westinghouse Electric Corporation, East Pittsburgh, PA (3)
Baldwin and Cradock, London (2)
Cooke, Troughton & Simms, Ltd., London (2)
Daniel Davis, Jr., Boston (2)
George Knight and Sons, London (2)
Johann Ambrosius Barth, Leipzig, Germany (2)
Leeds & Northrup Co., Philadelphia (2)
MacMillan and Co., London (2)
MacMillan and Co., London and New York (2)
Palmer House, Chicago (2)
Sampson Low, Marston, Searle, & Rivington, London (2)
Universal Scientific Company, Inc., Vincennes, IN (2)
Éditions du Journal Suisse d'Horlogerie et de Bijouterie, Neucha (2)
"The Electrician," London (1)
A. Lahure, Imprimeur-Éditeur, Paris (1)
Leeds & Northrup Company (55)
Magnetism (51)
Electrical Instruments (30)
Galvanometers (18)
Weston Electrical Instrument Corporation (15)
C5-C1 (14)
Theodolites (12)
Leeds & Northrup (10)
C3-G1 (9)
Telegraphy (7)
Telegraphs (6)
J. A. Fleming (6)
Abhandlungen zu der Lehre von der Reibungselektricität
An Account of Some Remarkable Applications of the Electric Fluid to the Useful Arts
Adjustments of Vernier & Micrometer Theodolites and Tacheometers
Advanced Theory of Electricity and Magnetism: A Text-Book for Colleges and Technical Schools
The Age of Electricity: From Amber-Soul to Telephone
Alphabet of Electricity for the Use of Beginners
The Alternate Current Transformer in Theory and Practice
"Amber Forever!": Electricity on the Merrimack in New Hampshire
Analysis of Some Methods of Supplying a Three Phase Induction Motor From a Single Phase Line
André-Marie Ampère - Immortalized by a German
The Annals of Electricity, Magnetism, and Chemistry; and Guardian of Experimental Science

redpajama_set_name: RedPajamaCommonCrawl


This Wedding card with Glitter Wedding Invitation Sets Also Invitation Card Design Intended For Your Extra Inspiration as the title was published on this site on Apr 15th, 2019. This picture listed as image numbe #956 in our album.
Press the back to article link below if you want to see the complete post titled Glitter Wedding Invitation Sets You Must Know. Or you also ca save them, the file size is about 0.527 MB with dimensions of 680x540 PX. And the MD5 code is e195a4b1c92a2a0a83b2b04985045815.


This hike is just slightly under 8 miles in length. We did it by shuttle with help from the friendly folks at the Hike Inn in Fontana. We parked the car at the Fontana Dam, they shuttled us (and our dog) back around to Yellow Creek Gap and we started from there.
About a mile in is Cable Gap Shelter which is practically right on the trail and has a nice little stream running past it. After Cable Gap there's a long climb through a series of knolls. Most of this section runs parallel to Fontana Lake and offers nice views. This picture shows a section of the lake and the dam.
Somewhere along here is Walker Gap where the Yellow Creek Mountain trail comes in. This does not appear to be a well marked trail but we'll save that for some future hike. From Walker Gap to the road at Fontana is an endless series of steep descending switchbacks (unless you happen to be hiking up / south / towards the NOC). There are several nice water sources through here and it ends at the road / marina / shuttle pick up for the Fontana Village (which also has restrooms). From there, the AT continues up and over a knoll along Fontana Lake before descending to the assorted parking areas.
Note that post 9/11 – this section of the trail will be closed during "security threats". There is an alternate path through Fontana Village and into the Great Smokies downstream of the dam. Just off to the right of this picture is the Fontana AT Shelter which is better known as the Fontana Hilton (because of its relative size for a shelter).
The interior of the dam is now closed to visitors although the overlooks are impressive. On the far side is the boundary of the Great Smoky Mountains National Park where the AT begins a grueling ascent to Clingman's Dome (30-some miles away by trail). The dam is probably more impressive when the spillways are open into the Little Tennessee River below.


text:
Westmoreland Elementary
We would like to thank all of the volunteers from ThermoFisher for visiting Westmoreland School. Our 4th grade students were absolutely captivated by the demonstrations, experiments and hands-on, strawberry DNA extraction. Thank you to Ron Durso and Lindsey Zarwi for developing this community partnership and bringing this experience to our students!
7 days ago, Westmoreland School
Our holiday concerts were outstanding! An enormous and heartfelt thank you to Mrs. Knitel and Miss. Cohen for their collaboration and planning! A special thank you to all of our classroom teachers and paraprofessionals who spent endless hours practicing songs and reinforcing lyrics! Each performance was excellent. Students were truly shining! We hope the sound of the children singing put you in the holiday spirit!
about 1 month ago, Westmoreland
Holidays Around the World! Many of our classrooms are learning about how different holidays are celebrated around the World! For example, St Nicholas Day is a favorite holiday celebrated in the country of Germany. On the night of December 5th, children clean and polish their boots and leave them outside their door before going to sleep. The next morning, they find their shoes filled with nuts, candy, and small gifts from St Nicholas. After learning about this holiday, some of our students found candy treats in their shoes too!
about 2 months ago, Westmoreland
Our Tiny Gallery of Gratitude is growing larger and larger each day and has provided us with a daily reminder of the how "little" and BIG things in our lives make us feel grateful.
2 months ago, Westmoreland
Grade 3 STEM: Building Basics Foam Block Tower Challenge In this Type 1 REACH Program, the third grade students are learning about the Engineering Design Process and the forces engineers must consider when building a structure. The students engaged in an engineering challenge to build a foam block structure that is a minimum of 10 inches tall and can withstand an earthquake. Some structures were stronger than others which led to a great discussion about how to make improvements.
Grade 4 STEM: Building a Shelter In this Type 1 REACH Program, the fourth grade students are using the Engineering Design Process to solve real-life problems. Their most recent challenge was to build a water-proof shelter in the Amazon Rainforest with only a few materials. The students worked in groups to design and build their shelters. Each shelter was tested with a spray bottle to determine if they could withstand the weather of the Amazon Rainforest.
Westmoreland Elementary16-50 Parmelee Ave.Fair Lawn, NJ 07410Phone: (201) 794-5490
Copyright © 2023 Fair Lawn Public Schools. All rights reserved. Powered By Thrillshare


Flags and Metadata (photools.com IMatch)photools.com - Digital Asset Management. User Community.
I don't see flags, dots or pins in rating label - are these only available in IMatch?
I clicked on Metadata in the dropdown list, IMatch Anywhere took a little time (more than a minute) to process this.
1. Is it possible to abort the operation? I really didn't want to get the metadata!
To see collections in the IMatch Anywhere WebViewer file window, enable the corresponding options in the layout drop-down menu.
The IMatch WebViewer help explains everything about this menu. Search for collection to find the corresponding info.
You clicked on "Metadata" in which drop-down list?
Do you mean you opened the Metadata panel in the Navigator on the left?
And it took a long time?
How many files were in the file window at that time?
What is your system and network spec?
Please always attach the IMatch Anywhere logfile when reporting performance. You can access it directly from the IMatch WebService Controller.
Through WAN not running locally.
This was more of a general comment when I make a mistake! If one clicks the wrong button, one can have to wait a while for result to be loaded if there are too many files. An ESC would be nice - but probably not possible, other than a reload/login again.
Usually this panel opens in a few seconds. Even it it has to load all data fresh from the server.
We would need the log file and the network traffic logged by your browser when you enabler the Debug mode (F12) to see what is taking so long.
All this panel is doing is to get the metadata for the files in the file window and then producing the grouping. 150 files is nothing and there should only be a very short delay, if at all.
Show us a screen shot of what the panel is showing.
And the IMWS log file from that session. See the log file help in the documentation to see where you can find this log. it is in the system TEMP ("c:\Windows\Temp" usually) folder, not your personal temp folder. This shows us timings, cache behavior, performance measures etc.
You can always press <F5> to reload WebViewer if you want to abort something that has no integrated cancel feature. But WebViewer is usually so fast that you don't need it.
WLAN can of course be a big issue. To diagnosis this we need to run your browser in debug mode so we can see the Network performance. Press <F12>, switch to the Network tab.


text:
Dear Superstar
Find out more about Dear Superstar here
Hard Rocking Amigos
It's been a while since we last caught up with hard rockers Dear Superstar and there have clearly been a few changes in that time. There's a new bass player for a start and it has to be said he fits the image better than the previous incumbent, infact the image all round has got a whole lot better; they look more like a cohesive unit these days, where before they just didn't look quite right as a band.
More important though is the material, it really sounds like they've been working hard and have knocked out some impressive tracks. Don't get me wrong, there wasn't anything majorly wrong with the old material but it lacked the killer hook and the big chorus, something they seem to have solved to good effect. Of course it's still glam metal but it's much catchier and to the point. Where they struggle today is with the tiny stage, it just wasn't built for five guys who really want to rock out and the poor old bass player is all too often sandwiched in-between front man Mickey and a guitarist or two.
Mickey is probably the most engaging front man in the building, it's nothing original but he plays the part very well and constantly moves around and when stuck in the middle of predominantly indie bands he really stands out. His attempts at crowd interaction don't really work today but that's more the fault of a fairly impassive crowd. The guitar parts are good and come through well despite the sound not being too hot and Benj's drums are probably the loudest in this venue all weekend.
There is the odd weaker song, 'Live Love Lie' for instance doesn't quite hit the mark but they make up for it with the superior 'Raised Voices & Confrontations'. Overall it's a good set in front of a hard crowd and they've put the work in over the last year to turn themselves into real contenders. It will be interesting to see if they can really capture the live energy when they head into the studio to record the second album.


text:
Media Studies » Search: *
Person: Kroft, Steve, 1945-
Person: Devine, L. Franklin, fl. 1993-2016
Media Studies(4)
Stewart, Jon, 1962-(3)
Boyle, Peter, 1935-2006(1)
Garrett, Brad, 1960-(1)
Romano, Ray, 1957-(1)
Television programs(4)
Satire(3)
all of Media Studies
60 Minutes, Jon Stewart
produced by L. Franklin Devine, fl. 1993-2016, Columbia Broadcasting System; interview by Steve Kroft, 1945-, in 60 Minutes (New York, NY: Columbia Broadcasting System, 2004), 12 mins
'The Daily Show' on Comedy Central has become must-see television for news junkies and politicians alike. And now, he's kicked up some dust by going after what Correspondent Steve Kroft calls 'the shouting matches that pass themselves off as cable news.'
L. Franklin Devine, fl. 1993-2016, Columbia Broadcasting System
Steve Kroft, 1945-
Columbia Broadcasting System
Jon Stewart, 1962-
Broadcast news, Television programs, Satire, Politics, Political and Social Movements
© 2004 CBS News
Broadcast news, Television programs, Satire, Politics
60 Minutes, The Daily Show With Jon Stewart
Steve Kroft interviews political satirist, Jon Stewart.
Broadcast media, Politics, Television programs, Satire, Family and Culture, Political and Social Movements
Broadcast media, Politics, Television programs, Satire
60 Minutes, The Daily Show With Jon Stewart (2002)
In a rebroadcast of an April 2001 segment, Steve Kroft interviews political satirist Jon Stewart about The Daily Show.
Politics, Comedy, Satire, Television programs, Political and Social Movements, Family and Culture
Copyright © 2002 by Columbia Broadcasting System
Politics, Comedy, Satire, Television programs
60 Minutes, Everybody Does Love Raymond
Before it airs its final episode, Everybody Loves Raymond is profiled on 60 Minutes. Steve Kroft reports.
Philip Rosenthal, Peter Boyle, 1935-2006, Patricia Heaton, 1958-, Brad Garrett, 1960-, Doris Roberts, 1925-2016, Anna Romano, 1963-, Ray Romano, 1957-
Comedy, Actors, Television programs, Television, Family and Culture
Comedy, Actors, Television programs, Television
Media StudiesAll of Alexander Street


As everything is made by hand for you each piece may vary slightly.
Orders are usually shipped with 2-3 weeks but if you would like it sooner please get in touch.
the item must be returned in its original state.
Shipping costs are non refundable and exchange shipping costs are the responsibility of the customer.
Some adjustments or repairs may incur a small fee.


AMT Coffee booth in central Oxford UK. AMT Coffee is a UK chain of coffeehouses mainly located in railway stations.
The Cafe de Flore is one of the oldest coffeehouses in Paris. Located on Boulevard Saint-Germain it's a famous hangout for artists and writers.
Starbucks Coffee shop in San Miguel de Allende, Mexico. San Miguel de Allende is a UNESCO World Heritage Site.
People sitting outside a coffee shop in Varkala,India.
The Corso Vittorio Emanuele II, with its characteristic Gothic and Renaissance edifices, many with frescoes. Pordenone, Italy.


text:
County schools announce registration dates
Nodaway County schools gear up for the start of a new year with registration dates and open houses. Jefferson C-123 •School starts Thursday, August 18. •Registration is 9 am to 4 pm, Thursday, August 11. •Open house is Wednesday, August 17; elementary is at 6 pm and junior high and high school are at 7
MDIO works to enhance downtown
Maryville Downtown Improvement Organization (MDIO) has its feet on the ground and has taken off running to improve the downtown district. MDIO became a reality in 2015, after talks in 2014 about establishing the entity. It is now part of Missouri Main Street, an organization that helps cities promote older main street and downtown business
1st Christian Church feeds carnival workers
The First Christian Church, Maryville, opened its doors to the late night carnival workers, July 13, and served breakfast to more than 35 individuals who were putting up rides and attractions for the Nodaway County Fair. Preparing the feast were Barbara York, Sandi Mull, Cara Shell, Marcia Jordan, Vicky Dougan, Sue Schenkel and Barb Pierce.
Get back-to-school shots now
It's important to get children's back-to-school immunizations as soon as possible, said Tabitha Frank, RN, BSN, Nodaway County Health Center public health nurse. Missouri state law changes have necessitated additional immunizations for children entering eighth and 12th grades for the 2016-17 school year. The two vaccines needed are the Tdap, which covers tetanus, diphtheria, pertussis
Losh Optometry shows dedication to service, Maryville
By Kathryn Rice Ryan K. Losh, OD, doctor of optometry, and his wife, Tracey, enjoy the Maryville community and schools so much that they made the commitment to start their own community business, Losh Optometry, 109 South Buchanan Street, Maryville. Losh practiced in Maryville from 2010 to 2011, after graduating from the University of Missouri-St.
BIG Art launches 2nd show
The Business Indoor Gallery of Art (BIG Art) sponsored by the Maryville Public Art Committee (MPAC) has launched its second art show. Display locations are: Accent Advertising and Signs, 114 East Third Street, has a two-piece painting by Brent Weiland. Accent is open from 9 am to 4 pm, Monday through Friday, for viewing. Regional
Skidmore to accept asbestos removal bids
The Skidmore City Council voted to accept bids for asbestos removal from the old city hall at the July 14 meeting. Skidmore citizen Don Richardson, a retired building inspector, was asked to inspect the building and gave a detailed report on the building condition. Aside from the roof, which Richardson said was in good shape,
Nothing screams summer like homemade ice cream
By Jacki Wood Editor's note: this is the last in a series of articles about summer ideas found on our Pinterest page. July is National Ice Cream Month, but no special designation is needed to know that summer is a perfect time for ice cream. Growing up, from Memorial Day to Independence Day to Labor
Pride, Host Lions Clubs complete challenges
The Maryville Pride Lions and Maryville Host Lions Clubs are two of the 12 Lions Clubs in district 26-M4 to complete all four of Lions Clubs International Centennial Challenges for the 2015-16 Lion year. Lions Clubs International started a three-year project in 2014 to serve 100 million people by the 2017 centennial anniversary of the
Parnell holds Duck Race activities


This Saturday (10th of February) will be the 182nd meeting of Arsenal and Chelsea since the introduction of the Football League! The game is one of English football's fiercest rivalries, and has become more and more competitive since the turn of the Millennium.
We've compiled TEN multiple-choice questions relating to this fixture down the years. This quiz will test your knowledge of the history of this fixture, as well as more recent events – all the events in this quiz have happened within the Premier League era, apart from a couple more general questions!


text:
Tag Archives: SUBSEA mission
Amusing Monday: A new hydrothermal vent field discovered off West Coast
The location of an unknown hydrothermal vent system was predicted by researchers studying maps of the seafloor along the Gorda Ridge off the West Coast. Following those leads, a group of underwater explorers looked for and found the shimmering cauldron of superheated water.
The discovery, during this year's Nautilus Expedition, took place about a week ago in an area about 75 miles offshore of the border between California and Oregon.
As operators dimmed the lights from their remotely operated vehicles, the sounds of excited scientists filled the mother ship's control room, where observers watched a video screen providing glorious views of the emerging flow (first video on this page).
"It's like an artist's rendition of another planet," tweeted volcanologist Shannon Kobs Nawotniak of Idaho State University, where her team figured out where to look for the vents using high-resolution sonar bathymetry. Researchers named it the Apollo Vent Field in honor of the 50th anniversary of the moon landing this year.
Check out more photos and videos on the Nautilus website, and learn more about the project in "The Alien Landscapes of the Apollo Vent Field."
The out-of-this-world reference to another planet was not an accident, as NASA researchers are contemplating deep-sea explorations of other worlds. For example, space scientists would like to send an unmanned craft to Europa, the sixth moon of Jupiter, where they would drill down through ice up to five miles thick to reach a volcanically active ocean. On the ocean floor of Europa, they might find hydrothermal vents with the right warmth and minerals to support life — possibly similar to the microorganisms that began life on Earth.
This year's Nautilus expedition involved a project known as SUBSEA, for Systematic Underwater Biogeochemical Science and Exploration Analog. The project, which ended about a week ago, is a partnership between the National Aeronautics and Space Administration, the National Oceanic and Atmospheric Administration and various academic research centers.
The Exploration Vessel (EV) Nautilus is a research platform equipped with two ROVs: the Hercules and the Argus. They are owned by Ocean Exploration Trust, founded in 2008 by Robert Ballad to explore the oceans.
Background on the SUBSEA mission is provided in a 26-minute video featuring lead scientists Darlene Lim of NASA's Ames Research Center and Christopher German of Woods Hole Oceanographic Institution (second video).
Gulf of California
On an entirely separate expedition in February, scientists aboard the Research Vessel (RV) Falkor from Schmidt Ocean Institute discovered colorful towers of minerals up to 75 feet tall in the Gulf of California. These towers, along with a variety of sea creatures clinging to them, were not there during a previous expedition a decade ago.
"Astonishing is not strong enough of a word," said Mandy Joye, a marine biologist at the University of Georgia who led the team that discovered the vents.
Check out the story "Deep-Sea Explorers Find Trippy, Rainbow-Colored Wonderland" by reporter Stephanie Pappas and the slideshow "Sea Life Thrives at Otherworldly Hydrothermal Vent System," both in the online magazine "Live Science."
Schmidt Ocean Institute, based in Palo Alto, Calif., is part of the Eric and Wendy Schmidt Network of Philanthropies. The institute owns the RV Falcone and supports its crew for teams of researchers from various institutions.
Coast of Oregon
The current expedition of the RV Falkor, led by Carolyn Ruppel of the U.S. Geological Survey, is studying methane seeps off the Oregon Coast. The cruise will add to ongoing knowledge about the hundreds of methane seeps that might become a significant contributor of greenhouse gas emissions.
Live video from the ROV SuBastian is available during operational periods. Click at the top of the "Live from RV Falkor" page to connect to the feed when it is available.
As I post this blog, the live feed is accessible (video below).
June 17, 2019 Benthic organisms, Climate change, Education, Humor, Oceans, ResearchHydrothermal vent, Methane seeps, Ocean Exploration Trust, Schmidt Ocean Institute, SUBSEA mission


text:
Beyond the Box Score homepage Horizontal - White Beyond the Box Score A Saber-Slanted Baseball Community
Follow Beyond the Box Score online:
Follow Beyond the Box Score on Twitter
Follow Beyond the Box Score on Facebook
Beyond the Box Score main menu
History & Hall of Fame
All About Sabermetrics
The Analytics Toolbox
SaberGraphics
MLB Playoffs 2016: for and against the Giants
The Giants went into freefall after the All-Star Break, but fate and an even year meant they still made the playoffs. Our writers make the case for rooting for the biennial champs, and for rooting against them.
By Travis Sarandos and Thomas Bennett Oct 5, 2016, 12:00pm EDT
Share All sharing options for: MLB Playoffs 2016: for and against the Giants
Joe Camporeale-USA TODAY Sports
Sometimes your favorite team doesn't make the playoffs, and if you're in that unenviable position this year, we at Beyond the Box Score want to help you decide who you're going to root for (or against) this postseason. We'll be publishing ten articles, one for each playoff team, with writers laying out the case in favor of and opposed to each team. In this, we tackle the darlings of the even year: the San Francisco Giants.
Root for the Giants
Travis Sarandos
When I was 25, I found my favorite sports bar. It was called Replay, and it was 1.5 blocks from my apartment on the Upper East Side of Milwaukee. Other than on Packer Sundays, it generally didn't do very well: the food was mediocre; the TVs were old, small, and discolored; it's most popular drink was the $2 Pabst Blue Ribbon tallboy; and on weeknights, its cavernous size made it look even more empty than it truly was. I loved it, and patronized it several times a week to watch baseball, hockey and basketball games; I was often the only person there who wasn't being paid. It was my "home bar," a thing that totally exists and is normal in Wisconsin, so just go with it. Imagine Cheers, except it's just me, a loud idiot, replacing all of the characters.
A year and a half ago, Replay closed its doors for good on the final day of the Packers regular season. It was replaced by a Rosati's, a popular chain restaurant/bar based in Chicago. The food is better (by several orders of magnitude), the place is always buzzing, and the TVs are much nicer and more plentiful. It looks like the place went through a visit from Bar Rescue, and it didn't even have to endure this man performatively screaming at morons. It's a much nicer place to watch games now. I hate it.
The point, of course, is that change is dangerous and terrible. There are certain things in life that one relies on. The sun rising in the East every morning; Mike Trout being the best baseball player alive but not the AL MVP; paying taxes (unless you're Donald Trump). You may not always love these universal constants, but they've always been there and always will be there, and that's comforting. So it is with the Even Year Giants, who have won the World Series every other season since 2010. World Series won by the Giants form the rhythm of our lives, and to root against them is to root for the hard, frightening unknown.
In addition to the existential appeal of the status quo, the Giants do have some very likable personalities to cheer for. Hunter Pence, the only barista at the university library's coffee shop who isn't enrolled in classes, is chief among them. Pence plays baseball like an ageless astral being who has been stuffed into a Grant Brisbee Halloween costume and watched one video of a baseball game played by 12-year-olds. That his mechanics work at the major league level is explained only by the realization that he is not truly of this earth. I mean my God, it worked, but what is this:
Beyond Pence, the Giants also feature baby-faced superstar Buster Posey, and the eminently likable ace Madison Bum- you know what? I'm sorry. I couldn't do it. There is, however, Giants neophyte Johnny Cueto, whose Instagram page is nearly as much of a strange but satisfying delight to look upon as his funky delivery.
Te vamos a extrañar
A photo posted by Johnny Cueto (@johnnycueto47) on Jul 1, 2016 at 11:19am PDT
Look, there are plenty of reasons to root against San Francisco, and a very wrong man who I'm sure is very nice is about to lay them out for you. I can't force you to stop reading now and ignore his slander of America's Team, so I'll leave you with the best argument I know how to make. In the final week of October during each of the Giants' last three World Series championship runs, pop sensation Taylor Swift has released an album so full of bangers that the British Isles were nearly stricken by another potato famine trying to provide enough mash to go with them. I would root for the malevolent demon hordes of Abaddon from the fiery pits of hell if it meant Tay would drop another platinum album. I hope you will too. Go Giants.
Root against the Giants
Thomas Bennett
Bless Travis Sarandos's soul. He was the unlucky someone on our staff who had to argue in favor of the Giants. Perhaps he enjoys a good challenge; perhaps he likes torturing himself.
Me, I prefer a nice, easy lay-up, and you can find no easier task than to convince the world that they should root against the San Francisco Giants in the 2016 postseason.
Sports fans can be jealous creatures, and I am not above appealing to this base emotion to make, really, the only point I need in my argument. Travis is a fan of a franchise (the Brewers) that has never won a World Series. I myself am a fan of a franchise (the Mariners) that has never even been to a World Series. There are many such fans out there that have never experienced the joy of their team capturing a World Series title, or for whom it's been so long that the memories have lost their luster. Here, in an orange and black nutshell, is the lynch-pin of any anti-Giants argument:
The San Francisco Giants have won three World Series titles in the past six years.
There is an undeniable air of expectation amongst Giants fans these days, which is understandable given their recent history success. That doesn't make it enjoyable, though. I recall visiting with some family (who happen to be Giants fans) in Northern California around August of 2014. We started talking baseball and noted that the Giants were, at present, five games back in the division. Five games back in the division would be cause for celebration around my neck of the woods, but this particular family member ruefully shook her head and muttered "They're terrible."
They would, of course, win the World Series two months later.
Maybe long-time Giants fans that stumble across this portion of the article would protest the broad brush that I'm painting them with. Well, I hate to break it to you guys, but any version of the long-suffering Giants fan that existed during the 1954–2010 drought has vanished.
I've long been accustomed to rooting for the underdog, but maybe our intrepid reader is more the front-runner type. In that case, I'd like to point out that it's not just the sheer volume of success in a such small amount of time that is off-putting, it's the manner in which these titles have come about. If you think the Giants have captured these three titles by simply being more talented than everyone else, think again.
For every Buster Posey, there's an Aubrey Huff. Every Madison Bumgarner, a Ryan Vogelsong. Every Travis Ishikawa, a Mike Morse... wait... er, my point is: every World Series run by this team seems to involve some seriously clutch performances from guys who almost immediately are out of the league or are just barely hanging on. If that's not annoying, I don't know what is. There are better underdogs and better front-running juggernauts than the Giants. They shouldn't make anyone happy.
In conclusion, unless you're really empathizing with all of those long suffering eighteen-month-olds in the Bay Area, cast your karma in with the rest of us and use whatever power you have at your disposal to help us end #EvenYearMagic forever.
More From Beyond the Box Score
Morning Mound Visit: MLBPA to make counteroffer Monday
Morning Mound Visit: 2022 season in jeopardy of a delay
Morning Mound Visit: Carlos Correa hires Scott Boras
Morning Mound Visit: Francisco Liriano announces retirement
One True Outcome: January 17
How much is Juan Soto worth? Let's try and guess what Soto's next contract will look like
Morning Mound Visit: MLBPA to make counteroffer Monday Plus, Stuart Sternberg's dumb idea is dead and robo umps are coming to AAA.
Morning Mound Visit: 2022 season in jeopardy of a delay The league hasn't negotiated in good faith and games might be lost because of it.
Morning Mound Visit: Jon Lester announces retirement The three-time World Champion is calling it a career
Morning Mound Visit: Carlos Correa hires Scott Boras The best free agent on the market switched agencies.


NASA has confirmed that SpaceX's uncrewed International Space Station (ISS) flight test mission will get underway in January 2019.
The launch is part of NASA's Commercial Crew Program, which involves the agency working alongside American aerospace industry as businesses develop and operate spacecraft and launch systems.
The goal of the program is "safe, reliable and cost-effective transportation to and from the International Space Station, which could allow for additional research time and increase the opportunity for discovery aboard humanity's testbed for exploration".
SpaceX's Falcon 9 rocket and Crew Dragon spacecraft (also known as Dragon 2) are scheduled to launch on 8 January (AEDT) from historic Launch Complex 39A at NASA's Kennedy Space Center in Florida.
Dragon 2 will fly a mission to the ISS to test the vehicle's systems in its first orbital flight. It will be an unmanned mission and aims to provide data on the performance of the Falcon 9 rocket, Crew Dragon spacecraft, and ground systems, as well as on-orbit, docking and landing operations.
If the initial test is successful, a follow-up mission called Demo-2 will take place next June, with NASA astronauts Bob Behnken and Doug Hurley planning on flying the Crew Dragon to the ISS.
In between these projects, SpaceX plans to test the Crew Dragon's abort system by jettison from a Falcon 9 vehicle after lift-off.
SpaceX last completed a pad abort test in 2015, which is a test of a launch escape system to see how adept the system is at evacuating the crew of a spacecraft in the event of an emergency on the rocket's launch pad.
Following the Demo-1 and 2 tests, NASA will "review the performance data and resolve issues as necessary to certify the systems for operational missions".


text:
<?xml version="1.0" encoding="utf-8"?>
<resources>
    <color name="colorPrimary">#00000000</color>
    <color name="colorPrimaryDark">#1C1F21</color>
    <color name="colorAccent">#285F8C</color>
    <color name="textColorPrimary">#1C1F21</color>
    <color name="textColorSecondary">#565B5E</color>
</resources>

redpajama_set_name: RedPajamaGithub


No, pinch me again. Harder this time.
For the love of God man, slap me across the face until I wake up from this utopian dream-scape! I crave reality and its harsh vastness of broken dreams. I want to return to earth.
I think I need a moment or two to compose myself.
We're meant to be emotional wrecks, unable to hold back tears as our talismanic forward Gareth Bale preps for his departure to Real Madrid and yet all I seem to be doing is counting the new signings this glorious transfer window has bestowed on us.
We have been nothing short of magnificent.
Magnificent. That's some accolade. For us to lose Bale and for the entire saga to be relegated to a footnote, a caveat, thanks to the business Levy, Baldini and Villas-Boas have done in bolstering our squad in practically every single area that requires further depth of quality. I say practically because there's still time for more to arrive.
I'm still gutted Bale is leaving and the fickleness of being a football supporter means that it's not too difficult to work through those five stages of grief and then find yourself immersed in hype surrounding new players. We like to move on fairly quickly. We do so because, deep down we all know we never go away. We are Tottenham. The players are only Tottenham for the duration of the time they wear our shirt. Not to underplay it, some players can enrich our history and traditions. Bale will never be forgotten. However, he could have truly cemented himself in folklore had he remained. But that's for another parallel universe to enjoy.
We have no Bale. We're stuck with Erik Lamela and Christian Eriksen.
I'll start with the latter.
Eriksen has not yet been confirmed, so unlike the pomp presented in written form for Willian, I'll hold back from my custom naked dance of jig in celebration until we have more concrete confirmation that the player is going to sign. It looks good at the moment. According to a variety of sources we've had a bid accepted and the player is discussing terms with the club.
Christian Eriksen – Ajax – age 20. He's an attacking midfielder. He's a little bit brilliant. Fits the Levy mantra (he's young and whatever we pay for him he's likely to be worth double that in five years time). Could prove an easier and cheaper option than some of the more celebrated targets that are entertained this time of year. We need some creativity, some inventiveness. We're lacking a spark. This Danish wonder-kid might be able to provide some.
I don't follow Dutch football to the degree of interest I follow La Liga and Serie A. My experience of Eriksen is Champions League football. One of the main issues that seems to surround his ability is wrapped in the hype that he generated during the 2010 World Cup and the expectations placed upon him where many believed he would elevate himself to super stardom. That never happened, but that isn't to say he hasn't progressed as a footballer. For a start, he's still a kid. 21 years of age. The problem of hype is everyone with those hedonistic expectations hoovered in anticipation whereas Eriksen has kept himself grounded.
Is he grounded because he can't improve any further? Or has he stagnated because he's remained in Holland? Or has he not stagnated at all with the critics being overly critical thanks to that expectation he promised?
He's played well without being consistently spectacular. But statistically (if that turns you on) he continues to score and assist. The split in opinion comes from people that (I'm guessing) have seen plenty of him.
Two schools of thought. One, he's not developed at that initial pace he displayed when he broke onto the scene. He's lightweight and positionally limited. The other is that people have been so critical of that lack of expected progression that they seem to believe he's over-rated, dismissive of the fact he's 21 years of age and has outstanding potential.
Eriksen is technically very good. Can pass, has pace, can play with both feet and creates. He needs a new lease of life and Spurs might be able to offer him that. It's really worth noting again...he's only 21.
I guess I have to trust AVB on this, as people that do follow the Eredivise are also split into two groups. I've been told he's wildly inconsistent, only plays well every so often. Then I'm told he's one of the best players in the league and for Ajax.
We need someone to provide that killer pass, that disguised through-ball. Can he fit into our 433? What does this mean for Sigurdsson? Will he rotate with Holtby? Will Carroll go out on loan?
Plenty of questions, all to be answered if...if he's signed.
As for El Coco? Roma have confirmed the transfer. Lamela has been quoted thanking their fans for his time there and looking ahead to his future at Spurs. We're still waiting for official word from Spurs. As per usual, running a bit late.
Now this guy is for me the quintessential Tottenham signing. If our other signings have been methodical requirements, Lamela is the glossy finish on the paint job. Proper box office footballer with the skills and trickery to back up the hype. A perfect antidote for the loss of Bale. Not similar players. Both in the same team would have been incredible. Instead, we're left with Erik and his own version of the heart celebration.
Plays out right, cuts in, scores. Dribbles (old skool). Is tough and elegant. Started out left for River Plate - so we've got someone who can perform across the pitch behind the forward - on both flanks or centrally (although based on his time at Roma, he'll start out wide and float inwards if required). A wonderful quote of his states that he '....plays wherever the coach wants me to play'. This is going to be exciting, seeing how he adapts into the English game and more so how we plan to use him.
He's Argentine. We have form for this sort of thing.
Roma fans absolutely devastated that he's been sold. Hand on heart, I'm actually shocked he's been sold. Another very young, highly talented and highly rated player with the world at his feet. A player that many are citing as one that can go on to be one of the best. I guess we should seek to retain our own feet on the ground. Much like the hype Eriksen was subjected too, we might need a touch of patience.
Kudos to Baldini on bagging Lamela (again). Eriksen is well worth the gamble. We've also got Vlad Chiricheș on his way (apparently he cried when Steaua initially rejected our first approach for him). A centre-back that can deputise at left-back.
We've required that creative spark and trickery. We might have competition for the number 10 role. That bit of magic, that something different to work along side the strength and midfield presence we have in abundance.
In both of these players we appear to have found the missing ingredients. We may need to slow cook before we're dished and treated to a feast, but there's no denying the table has been booked. Over to the head chef. Lasagne isn't an option.


Lori Bastien, Philip Keveran, Randall Hartsell, and Nancy Bachus.
and repertoire. I am a contemporary style teacher with a gentle and patient personality.
all other styles of music.
It is easier for me to respond to you quickly with email about available times, rates, and starting lessons.


Contact me at noelle@gingerhaze.com or follow me on Tumblr or Twitter.
Noelle Stevenson is the New York Times bestselling author of Nimona, has been nominated for Harvey and Eisner Awards, and was awarded the Slate Cartoonist Studio Prize for Best Web Comic in 2012 for Nimona. A graduate of the Maryland Institute College of Art, Noelle is a writer on Disney's Wander Over Yonder, the cowriter of Boom! Studios' Lumberjanes, and has written for Marvel and DC Comics. She lives in Los Angeles. In her spare time she can be found drawing superheroes and talking about bad TV on her Tumblr or on Twitter.


text:
Snowcat Ridge reopens, has seven days to avoid being closed again by Pasco County
The sledding park says it addressed the "unsafe" conditions. But it must pass more inspections or Pasco County officials say they will shut it down again.
DADE CITY — The Snowcat Ridge alpine sledding park reopened on Friday, a day after Pasco County officials shut it down for numerous safety violations.
But it opened under a seven-day temporary certificate of occupancy granted by the county. Snowcat Ridge will be closed again if it doesn't pass final inspections by then, said Pasco County spokeswoman Tambrey Laine.
The park fixed its most pressing safety issues and was cleared by inspectors, Laine said. The temporary permit allows it to re-open but with limitations until a follow-up inspection is completed.
In a statement to the Tampa Bay Times, the park's operator announced it reopened on Friday but did not address the seven-day deadline.
"After a thorough inspection by Pasco County this afternoon, we've addressed the issues reported by Pasco County officials" said park spokeswoman Vanessa Evans.
The operator said it "temporarily removed" shipping containers in the Alpine Village area. Many of the code violations county officials said they found centered on those containers.
"They have corrected the imminent life-safety violations," Laine said.
Snowcat Ridge opened on Nov. 20 with a 60-foot sledding hill, an Arctic Igloo where kids can play in the snow and an Alpine Village with picnic tables and vendors. It markets itself as Florida's first and only alpine snow park.
But Laine said the park should never have opened in the first place. It lacked a certificate of occupancy and only one of three required permits were approved by the county. Evans did not respond to a request for comment about the county's statement.
Pasco County officials said they became aware of the issues on Nov. 25. The park said county inspectors arrived on Wednesday. The county shut the park down on Thursday after inspectors said they found electrical, fire, building and plumbing code violations that posed a "significant threat to public health and safety."
Related: Pasco shuts down Snowcat Ridge for 'unsafe' conditions, code violations
When an owner or contractor applies for a permit seeking county approval for any kind of construction work, inspectors must examine the finished work and approve it.
But Pasco County says Snowcat Ridge skipped that step. The project sought permits but never sought final inspections. When it opened on Nov. 20, the county said just one permit had been inspected and passed that inspection. But the attraction failed to seek inspections to close out two other outstanding permits, according to the county.
County officials released 48 photos that inspectors took that they said showed "unsafe" conditions, particularly in regards to the power set-up and shipping containers used as structures.
Pasco County believes the attraction will obtain a full certificate of occupancy before the temporary certificate expires, Laine said.
"The safety of our staff and guests are our top priority and with these modifications complete, we are looking forward to welcoming guests back to Snowcat Ridge," the park's operator said.
The county is considering creating a position that would work full-time with business owners of "complex projects" to ensure they obtain all the required paperwork and inspections before they open, Laine said. The idea is to ensure that situations like what happened at Snowcat Ridge this week don't happen again.
"It's in the county's best interest, of course, to have an attraction like this open," she said. "We want to work with the company to ensure they can continue to operate in a safe environment."
Up next:Pasco Commission votes to now allow alcohol sales on Sunday mornings