- Update ShortService and LongService constructors to accept db Session parameter for proper dependency injection instead of using module-level db instance
- Reorganize imports in memory_short_term_controller.py following PEP 8 conventions (stdlib, third-party, local imports)
- Add comprehensive docstrings with type hints to ShortService and LongService methods for better code documentation
- Fix import organization in memory_short_service.py to group related imports and improve readability
- Reorganize imports in user_memory_service.py to follow consistent import ordering patterns
- Update ShortService instantiation in analytics_memory_types to pass db parameter
- Remove module-level db instance initialization in favor of caller-managed database session lifecycle
- Add type annotations to method signatures (end_user_id: str, db: Session, return types)
- Improve code formatting and spacing consistency across memory service files
* [add]Create a workspace and initialize the default ontology engineering scenario
* [add]The language parameters for creating the workspace determine the default language for switching in the ontology project.
* [changes]Standardized return format
* [add]The default ontology is associated with the default configuration.
* [add]Create a workspace and initialize the default ontology engineering scenario
* [add]The language parameters for creating the workspace determine the default language for switching in the ontology project.
* [changes]Standardized return format
* [add]The default ontology is associated with the default configuration.
* [fix]The log retains genuine alerts and errors, while filtering out unnecessary noise.
* [fix]Scenario English and Chinese, emotion specifications
* [fix]Change the "no data" scenario from 0.0 to None
* [fix]The emotional health indicators, emotional advice, and emotional distribution analysis are all linked together.
* [fix]The emotional health indicators, emotional advice, and emotional distribution analysis are all linked together.
* [fix]Separate expected errors from unexpected errors
* [fix]The log retains genuine alerts and errors, while filtering out unnecessary noise.
* [fix]Scenario English and Chinese, emotion specifications
* [fix]Change the "no data" scenario from 0.0 to None
1. when adding a model API key to the model list, a tenant_id uniqueness check needs to be added;
2.the Model Square has cancelled custom models;
3. optimization of the interface logic for customizing model configurations in the model list
* [add]Integration of the core engineering and memory extraction
* [add]The import and export function of the main body engineering files
* [add]Improve the import interface
* [add]Introducing generic types helps with entity extraction
* [add]Modify the references of the main repository to the sub-repositories
* [add]The extraction trial run introduces the ontology type.
* [add]Integration of the core engineering and memory extraction
* [add]The import and export function of the main body engineering files
* [add]Improve the import interface
* [add]Introducing generic types helps with entity extraction
* [add]Modify the references of the main repository to the sub-repositories
* [add]The extraction trial run introduces the ontology type.
* [add]Complete the second phase of the main project content
* [add]The dependencies and configurations of the main body project
* [add]Modify the code based on the AI review
1. Three party web website data access - Web site synchronization
Building a knowledge base by crawling web page data in batches through web crawlers
Web site synchronization utilizes crawler technology, which can automatically capture all websites under the same domain name through a single entry website. Currently, it supports up to 200 subpages. For compliance and security reasons, only static site crawling is supported, mainly used for quickly building knowledge bases on various document sites.
2. Feishu Knowledge Base
By configuring Feishu document permissions, a knowledge base can be built using Feishu documents, and the documents will not undergo secondary storage
3. Language Bird Knowledge Base
You can configure the permissions of the language bird document to build a knowledge base using the language bird document, and the document will not undergo secondary storage
