Purpose and Scope
Alfresco Search Services delivers search functionality to Alfresco in a component that can be updated independently from the core. It was introduced with 5.2 and brings Solr 6.3 to Alfresco.
Documentation
http://docs.alfresco.com/5.2/concepts/search-home.html
Artifacts
Community Edition:
Enterprise Edition:
- Alfresco Support Portal
- Enterprise Artifacts Repository
Governance Model
The roadmap of the project is determined by Alfresco Product Management in response to customer needs and analysis of the market place. Open source contributions are considered for inclusion based on their quality, relevance to the current roadmap, and our quality assurance backlog.
License
Alfresco Search Services is made available under the terms of the LGPLv3.
Source Code
See https://github.com/Alfresco/SearchServices
Issue Tracker
The team works from the "Search and Discovery (SEARCH)" project at http://issues.alfresco.com.
The public can raise issues in the ALF project at http://issues.alfresco.com, and they will be linked into the appropriate project during triage.
Subscribers to Alfresco support should report issues through the Alfresco Support Portal, so that they can be properly tracked and escalated.
Road Map
We are still working on publishing a road map.
Customers can escalate feature requests through Alfresco Support.
Architecture
The Enterprise Edition product is built on top of the Community Edition core.
We are also working on releasing the test framework and test cases for the features included in the open source module.
We are working on documenting the architecture.
Contribution Guidelines
Contributions should be submitted as patches in the ALF project at http://issues.alfresco.com We will need you to sign a Contribution Agreement before we can accept your contribution.
If you are interested in making a large contribution, please reach out to us before starting work so that we can discuss the likelihood of our accepting the contribution. In our experience, most large contributions to the ECM Repository are better implemented as modules.
All contributions should have an associated test case.
