Storing and identifying content through content descriptors in a historian system
Annotating content, comprising data values of one or more tags corresponding to a process device within a continuous process, with content descriptors in a historian system. Content descriptors enable indexing and saving content within a search service database for later retrieval by search strings that match the content descriptors. Content having one or more common content descriptors are retrieved and transmitted to a client computing device via a communications network for displaying in a dashboard on the client computing device.
1. A historian system comprising:
a processor;
a database storing content relating to a plurality of process devices within a process; and
a memory device coupled to the processor and further comprising processor-executable instructions stored in the memory device for, when executed by the processor:
receiving, at a client layer of the historian system, content descriptors for the content, the content descriptors comprising data values of one or more tags corresponding to the process devices within the process, the content descriptors describing the content,
formatting, at the client layer of the historian system, the received content descriptors into a language-independent data format,
queueing, at a service layer of the historian system, the formatted content descriptors in an indexing queue as messages,
indexing, at the service layer of the historian system, according to an order of the indexing queue, the messages containing the formatted content descriptors in the database, the indexing comprising assigning a status descriptor to each message during each stage of the indexing, the indexing enabling the formatted content descriptors to be found in the database upon the status descriptor of a respective message being a stage corresponding to a successful indexing, the indexing enabling the stored content relating to a plurality of process devices to be selected and retrieved based on the found content descriptors;
dequeuing, at the service layer of the historian system, each message previously queued within the indexing queue from the indexing queue, the dequeuing of each message being enabled and performed upon the successful indexing of each message in the database; and
providing the selected content corresponding to one or more of the process devices within the process based on the content descriptors found in the database.
2. The historian system of claim 1 , wherein the content descriptors comprise at least one of a content name and a keyword annotation of content.
3. The historian system of claim 1 , further comprising:
searching the indexed content descriptors in the database in response to requests; and
providing indexes of content descriptors stored in the database matching the requests.
4. The historian system of claim 3 , further comprising providing a dashboard via a network connection, the dashboard comprising the selected content having one or more common content descriptors.
5. The historian system of claim 1 , wherein the language-independent data format is a JavaScript Object Notation (JSON) format.
6. The historian system of claim 1 , further comprising receiving the content descriptors and responding to requests via a network connection.
7. The historian system of claim 6 , wherein the historian system is coupled to a plurality of client devices.
8. The historian system of claim 7 , further comprising providing a dashboard to each of the plurality of client devices, the dashboard comprising content having one or more common content descriptors.
9. A method comprising:
storing, in a database, content relating to a plurality of process devices within a process;
receiving, at a client layer of a historian computing device, content descriptors for content, the content comprising data values of one or more tags corresponding to the process devices within the process, the content descriptors describing the content;
formatting, at a client layer of the historian computing device, the received content descriptors into a language-independent data format;
queueing, at a service layer of the historian computing device, the formatted content descriptors in an indexing queue as messages;
indexing, at the service layer of the historian system, according to an order of the indexing queue, the messages containing the formatted content descriptors in the database, the indexing comprising assigning a status descriptor to each message during each stage of the indexing, the indexing enabling the formatted content descriptors to be found in the database upon the status descriptor of a respective message being a stage corresponding to a successful indexing, the indexing enabling the stored content relating to a plurality of process devices to be selected and retrieved based on the found content descriptors;
dequeuing, at the service layer of the historian system, each message previously queued within the indexing queue from the indexing queue, the dequeuing of each message being enabled and performed upon the successful indexing of each message in the database; and
providing, by the historian computing device, the selected content corresponding to one or more of the process devices within the process based on the content descriptors found in the database.
10. The method of claim 9 , wherein the content descriptors comprise at least one of a content name and a keyword annotation of content.
11. The method of claim 9 , further comprising:
searching, by the historian computing device, the indexed content descriptors in the database in response to requests received via a communications network; and
providing indexes of content descriptors stored in the database matching the received requests.
12. The method of claim 11 , further comprising providing, by the historian computing device, a dashboard comprising the selected content having one or more common content descriptors.
13. The method of claim 9 , wherein the language-independent data format is a JavaScript Object Notation (JSON) format.