Citrine

Improvements
* We added a tool that scans the repository for outdated annotations and other deprecated aspects of the API. It raises a flag when it finds an issue. 654
* Design workflow executions that were taking a long time would time out and fail with an opaque error message. The error message now includes the execution's unique ID for easier debugging. 666
* We added `read_to_memory` to the GEMTables interface. This method allows you to download a table (formatted as a CSV in a string) into a variable rather than requiring a round-trip to disk. 667

Fixes
* Previously, the `pandas<=1.1` and `numpy>=1.2.0` combo would cause numpy to throw `dtype` alias deprecation warnings. We changed the pandas dependency requirement to `pandas>=1.1.0` to avoid these warnings. 659
* The documentation on predictors used out-of-date argument names when illustrating how to use chemical formula and molecular structure featurizers . They have been updated. 660
* There were a few private methods whose names did not have a leading underscore. We fixed that. 663
* Added a setter method to fix a minor issue regarding the `TableConfig` class's `uid` attribute. 664

What's New
* A new builder module for auto-configuring platform assets. Users can create an `AutoConfigureWorkflow`, which configures default assets starting from a material, GEM table, or predictor. 653

Improvements
* An alias for accessing the Citrine-scope UID on all data concepts objects by calling `object.uid`. 658
* An alias on Table Configs for accessing the field `config_uid` by simply calling `config.uid`. 655

Fixes
* Warnings are by default enabled for deprecated methods. 656

This release includes the addition of a new collection `GEMDResourceCollection` for accessing generic data objects from the Citrine Platform. Users can now get, list, register, update, and delete GEMD objects, regardless of their type, through methods on this generic collection accessed by `project.gemd` or `dataset.gemd`.

What's New
* Client support for interacting with generic data objects on the Citrine Platform. 646

What's New
* Defining the components of Table Configs can now be done using Templates or IDs instead of just LinkByUIDs. This matches the access patterns of other elements of the citrine-python API and should be more convenient for using a collection of GEMD Objects to build exactly the table you need. 648

Improvements
* We now handle URLs with a wider range of characters for scopes and identifiers. We now have full support for all characters allowed by the [GEMD specification](https://citrineinformatics.github.io/gemd-docs/specification/unique-identifiers/#alternative-ids). 650

Fixes
* Plus some documentation and test fixes 647 649

This release contains some of the last few (non-breaking) changes in support of releasing v1.0.0.

What's New
* The ability to list archived design workflows (631, 637). Archiving resources is a good way to keep your workspace clean, but sometimes you want to restore a resource and you might not remember the uid. Now you can list all of the design workflows you've archived.
* All updates to GEMD objects can be performed using the `update()` method (640). Some updates to GEMD objects are long-running, because we have to verify that the update does not invalidate any objects in the database. The method `async_update()` handles this case. But it can be tough to remember which types of updates require the asynchronous call. Now you can safely use `update()` for all your GEMD update needs, and citrine-python will automatically make the call asynchronous when appropriate.

Improvements
* Updates to the Graph Predictor documentation (633)
* Uniform use of `uid` when the type of resource being identified is obvious (635). For example, `DesignWorkflowCollection.archive(uid)` instead of `DesignWorkflowCollection.archive(workflow_id)`. This pattern was already used in most places, but is now consistent. The old arguments will be valid until at least version 2.0.0, for backwards compatibility.
* Slight reorganization of the file structure, for consistency (634). Current import paths will continue to work until at least version 2.0.0. Look out for warnings indicating an updated path.

Fixes
* Old resources featuring deprecated objects are skipped over during listing, instead of throwing an exception (641).

Coming Soon
* Citrine-python v1.0.0 release!