Attribute Spaces ================= .. code-block:: http /api/repositories/{repository}/entities/{entity}/attributes/{attribute}/values/spaces .. csv-table:: :header: Parameter, Type, Purpose :widths: 20, 20, 60 :stub-columns: 1 repository, string, The :doc:`repository ` name entity, int, The :doc:`entity ` ID attribute, int, The :doc:`attribute ` ID .. http:get:: /api/repositories/(string:repository)/entities/(int:entityID)/attributes/(int:attributeID)/values/spaces :synopsis: Get all data rows where the value for an attribute is 1 or more spaces Gets a complete list of data rows where the value for an attribute is 1 or more spaces. .. code-block:: http GET /api/repositories/jupiter/entities/1/attributes/3/values/spaces HTTP/1.1 Accept: application/json The list of rows may be quite long; if so, the list can be paged: .. http:post:: /api/repositories/(string:repository)/entities/(int:entityID)/attributes/(int:attributeID)/values/spaces :synopsis: Get a partial list of data rows with a null value for an attribute Get a page of rows where the value for an attribute is 1 or more spaces .. code-block:: http POST /api/repositories/jupiter/entities/1/attributes/3/vakues/spaces HTTP/1.1 Content-Type: application/json { "command": "get", "options": { "pageStart": 1, "pageSize": 32 } } The response will be a :doc:`standard-response`, with a list of records in the corresponding :doc:`entity` with a null value for the attribute. The ``columns`` array will contain the list of columns for each ``dataRow``. ``rows`` will contain the list of records of the corresponding :doc:`entity`. If there are no records in the :doc:`entity`, ``rows`` will be an empty string. Export ------- Some or all of the rows may be exported as a scheduled task. .. code-block:: http POST /api/repositories/jupiter/entities/1/attributes/3/values/spaces HTTP/1.1 Content-Type: application/json { "command": "export", "data": { "filename": "filename.csv", "filetype": "csv", "encoding": "utf-8" }, "options": { "where": "Row = 21" } } .. csv-table:: :header: Response Code, Reason :widths: 25, 75 200, No error 400, Invalid data passed with request 500, Server error The request packet must contain the ``command`` and ``data`` elements. The ``options`` element is not required, but may specify the columns to export, and/or the rows to filter. The following table shows which fields are required in the ``data`` element: .. csv-table:: :header: Field, Required :widths: 20, 10 filename, Y filetype, N encoding, N If ``filetype`` is not specified, it defaults to csv. If ``encoding`` is not specified, it defaults to the server native encoding. The response will contain the URL of the scheduled task and the link to download the exported file. .. code-block:: json { "job": "/api/repositories/jupiter/scheduler/1", "file": "/api/repositories/jupiter/download/filename.csv" }