Find Jobs
Hire Freelancers

Drupal / SOLR / DB2 Questions

$30-250 USD

Dibatalkan
Disiarkan hampir 14 tahun yang lalu

$30-250 USD

Dibayar semasa penghantaran
READ THIS FIRST: To bid for this project, you MUST have strong Drupal and SOLR skills and experience integrating these together in non-standard environments. We must get a strong sense of your skills in your initial communication and have some confidence that you have thoroughly read and understood our [login to view URL] is not On-the-Job-Training. Generic messages such as "We have reviewed your requirements and can help you. Please award us the project." will not be answered. Further, we will flag your company in our database and will automatically disqualify you from future bidding opportunities. SITUATION We have a few different Drupal implementations either under development or in the planning stages. We need some help in architecting appropriate solutions and solving a few current issues. We have a variety of questions around the following subject areas (in decreasing order of precedence.) - Drupal - SOLR Integration - Drupal - DB2 Integration - Drupal module selection - Drupal implementation (General) For your reference, we have listed our scenarios as well as specific questions which are outstanding. We need for you to provide detailed responses to our queries and help us solve these issues. If you are unable to solve every issue, please tell us the issues you can solve and provide a quote for those issues. If you can satisfactorily answer these questions (paid of course), we may also want to work with you on future Drupal/SOLR implementation and integration issues for us. With the exception of DB2, we will be doing a lot with these other technologies (i.e. Drupal, SOLR) in the future. NOTE: Our choice of Drupal or other tools in these scenarios is not up for review. If you have a better technology option, we would love to hear about it, but these sites will all have to move forward with the technologies listed. SCENARIO ALPHA - DRUPAL <-> SOLR <-> DB2 INTEGRATION We are preparing to implement several Drupal sites in an organization. In order to maintain consistency, the organization will use Drupal for all web sites. One of the planned Drupal sites appears to be problematic. This site will be based around a LAMP configuration. The actual Drupal database will be a MySQL database. This site will not implement the typical functionality included in a normal Drupal site. Rather, the site will serve as a front-end for approximately 100 "reports" whose data will come from a DB2 version 9.5 database. Approximately half (50) of these reports will be public-facing. The other half of the reports will be secured. The client does NOT have a separate reporting engine. All of the reports will be selected, executed, and displayed within Drupal. Most of these reports will include a query filter of 1-5 fields (with the average being 3 fields). Example query filter fields might be selection of a department, date range, etc. Query filter fields may be dependent on each other. The choice of query filters will vary from report to report with some overlap. Query filter forms will need to be developed in Drupal (perhaps using the Form API) and query parameters information transmitted to and executed against the DB2 database and the results displayed in Drupal. Most of the result sets returned will contain table data and will be displayed as tables within a Drupal page. For sending query requests to DB2 from within Drupal, someone had suggested using an XML gateway. The client's staff must be able to periodically add new reports. While this staff has some development background, their skill is limited. We are looking for the simplest/most efficient mechanism to allow them to 1) add a menu item for the report, 2) add query filters, 3) execute the query, and display the report on screen. To the maximum degree possible, we would like to limit the amount of development required by the client's staff. 1.1. What is the best way to develop report filters in Drupal--perhaps even allowing report filter elements (e.g. Date Range - as in fiscal year) to be re-used across reports? 1.2 What is the best way to actually send query requests to DB2 and have them processed on the DB2 Server? 1.3 What is the best way to return the query results from the remote DB2 server and to process them on the local machine. 1.4 How could data from the DB2 database be indexed within Apache SOLR and then searched within Drupal? 1.5 Some of the DB2 database tables link to external documents stored on the file system. How could these documents be indexed and searched within Drupal? 1.6 What is the best way to add new reports to Drupal--while minimizing the impact on the client's staff? 1.7 If we want to index all of the documents in a specific file directory (e.g. TIFF images of scanned documents), can we do this directly with SOLR, or do we need Nutch? (I realize TIFFS are quite legacy but in this instance conversion to PDF is not an option.) 1.8 Regarding question 1.7, is there an easy way to convert TIFF files into searchable PDFs for use with SOLR? SCENARIO BETA - DRUPAL <-> SOLR <-> MULTIPLE LEGACY SITES We are implementing a Drupal site in organization which has many departments. Each of the departments currently have their own legacy sites. The organization plans to utilize Apache SOLR as its primary search tool. The organization wants to be able to index both its Drupal site and its legacy sites and have the content from all sites appear in the search results within Drupal. However, the organization is running into some issues. They have made some attempts to combine the [login to view URL] file that comes with Apache SOLR Search Integration as well as Nutch. While it appears the documents are indexing, they do not appear within Drupal. We've read about issues with this approach that even once the schemas are combined, the lack of a true numeric ID from the Nutch documents still prevents Nutch documents from appearing in search results in Drupal. 2.1 Do we need to consider the possibility that the lack of a true numeric ID from the Nutch documents is preventing Nutch documents from appearing in Drupal? If so, h How do we get around this problem? 2.2 Another approach I've seen is to use a nightly build of Nutch 1.1 which allows customization of the schema that Nutch uses to push documents into Solr. Is this a better solution? What is the best way to setup this schema so that the search results show up in Drupal and the fields are mapped to the most appropriate places? Where is there a good listing of the available fields from Nutch and what they contain? Does the non numeric ID problem mentioned above also apply here? 2.3 How would this organization be able to combine content from both legacy and Drupal sites and have that information all appear in the search results?
ID Projek: 708092

Tentang projek

3 cadangan
Projek jarak jauh
Aktif 14 tahun yang lalu

Ingin menjana wang?

Faedah membida di Freelancer

Tetapkan bajet dan garis masa anda
Dapatkan bayaran untuk kerja anda
Tuliskan cadangan anda
Ianya percuma untuk mendaftar dan membida pekerjaan
3 freelancers are bidding on average $217 USD for this job
Avatar Pengguna
please check PM for details
$200 USD dalam 2 hari
4.9 (226 ulasan)
8.0
8.0
Avatar Pengguna
Hello! We are a strong team of Drupal experts proficient in creating various community websites, social networking systems, etc. Drupal based and would be able to handle your project and enable it with all required features and fucntionality. Please check PMB for more detailed proposal.
$250 USD dalam 5 hari
5.0 (2 ulasan)
1.9
1.9
Avatar Pengguna
we would be able to provide you the required services
$250 USD dalam 5 hari
0.0 (0 ulasan)
0.0
0.0
Avatar Pengguna
1.1. --The best way varies on the quantity of data and desired access. Views module can provide reasonable filtering for date ranges or Solr can have additions to allow it to return results based on a date range. 1.2 --PHP has DB2 connectors that can be installed. It is probably easiest to install the DB2 connectors for PHP, define a secondary DB in the settings file for DB2, and send requests to DB2. It would be straightforward to provide XML requests to the DB2 server as well, however, that would require additional work on the part of the DB2 site maintainers. 1.3--ame as 1.2. If by process on DB2 Server vs process on the local machine you are suggesting aggregation of results from the database, then an XML communication would be suggested for 1.2 and the current answer to 1.2 would be suggested for 1.3. 1.4 --The data would need to be surfaced – at which point it could be crawled with Nutch – or pushed into the index – requiring development on the DB2 side. Once the content is in the index, any content in the index can be retrieved via Drupal. Note that surfacing results would be atypical, however, in that there would be no “page” to navigate to from the search without pulling the content into Drupal or providing an external-facing page that can be accessed. DB2 data could also be entirely ingested into Drupal and then pushed into the Solr index. 1.5 --Issues similar to 1.4 would exist, however, pushing documents into the index would only require the installation of the Tika extension to Solr. Tika allows documents to be scanned, indexed, and retrieved via Solr. Like 1.4, once the items are in the index, they would show in results, but retrieving the file would require the file to be in Drupal, externally accessible, or retrieved via custom code in Drupal. Note that I do not believe that Tika will be able to turn images into text that can be indexed. If the goal is to have the content be indexed and searchable via keywords, it would be suggested that the documents are tied to a “content” item, fleshed out with keywords or other metadata, and served via the content item rather than directly – in this case Tika would not be necessary. 1.6 --If we are accessing the DB2 system directly, there need be little to no impact on the client’s staff. If the access is done via an api of some sort (xml), then the xml api will need to allow for this sort of flexibility up front. 1.7 --Items can be pushed into the Solr index at any time via a variety of means. Drupal does not provide a directory-scan style import of items nor does Solr independently. Nutch would allow you to scan over the available items for import into the index, however, without context the TIFF images would not be searchable in a meaningful fashion. 1.8 --We are not currently aware of any tool that will convert TIFF images into searchable PDFs, though commercial solutions may exist of which we are unaware.
$200 USD dalam 10 hari
0.0 (0 ulasan)
0.0
0.0

Tentang klien

Bendera UNITED STATES
Ellisville, United States
2.5
3
Kaedah pembayaran disahkan
Ahli sejak Feb 9, 2010

Pengesahan Klien

Terima kasih! Kami telah menghantar pautan melalui e-mel kepada anda untuk menuntut kredit percuma anda.
Sesuatu telah berlaku semasa menghantar e-mel anda. Sila cuba lagi.
Pengguna Berdaftar Jumlah Pekerjaan Disiarkan
Freelancer ® is a registered Trademark of Freelancer Technology Pty Limited (ACN 142 189 759)
Copyright © 2024 Freelancer Technology Pty Limited (ACN 142 189 759)
Memuatkan pratonton
Kebenaran diberikan untuk Geolocation.
Sesi log masuk anda telah luput dan telah dilog keluar. Sila log masuk sekali lagi.