Daylight | Cloud | 2020-07-18

Enhancements

  • Daylight: Reordered feature list

  • API client: New features available

Daylight: Reordered feature list

Now, the feature icons in the sidebar in Daylight are also reorganized: 

  • Highlights

  • Volume

  • Galaxy

  • Drivers

  • Sentiment

This change helps to guide users more intuitively through the application. Each Daylight feature pairs well with another feature for various stages of analysis. When initially discovering concepts, some users may prefer the visual Galaxy view, while others may prefer to look at the metric-oriented Volume feature. Some users might prefer to explore the spirit of a dataset through Sentiment, and others might consult quantitative Drivers metrics.

Along with this update, we also reorganize the cards on the Highlights feature. Now, the cards are ordered as follows: 

  • Which concepts are most prevalent? — This card displays a snapshot of the Volume feature. 

  • What are the largest clusters of conversation? —This card displays a snapshot of the clusters you view in the Galaxy. 

  • What issues are affecting [score field]?  —This card displays suggested drivers based on score fields included in your metadata.  

  • What do people feel strongly about? — This card displays concepts Daylight detected as displaying strong sentiment

API Client: New features available 

With this release, there are two new features available in the API client:

  • Now, when you create an instance of the API client, you can specify a timeout option. Before, if you made a call to the server with the API client that never returned, the script would wait forever. Now, if you set a timeout, it raises an exception if it has not received a response within the amount of seconds for which you specified the timeout.

  • If Concept-Level Sentiment is enabled in your Daylight Cloud environment, you can use a new wait_for_sentiment_build() method. Since new Concept-Level Sentiment science is calculated after the core project build, you can use this new command in the same way the existing wait_for_build() method waits for the core project build to finish, wait_for_sentiment_build() waits for the Concept-Level Sentiment build to finish. Since Concept-Level Sentiment always finishes after the core project build, this is useful for scripts that use the API to build a project and then get sentiment data from it.
    Note: If you use wait_for_sentiment_build() method in the updated API client before Concept-Level Sentiment is enabled for you, you will receive an error message.