Drupal Development

From BarbWiki

(Difference between revisions)
Jump to: navigation, search
Line 5: Line 5:
Suggested solution
Suggested solution
-
1.  Records uploaded to CONTENTdm
+
#Records uploaded to CONTENTdm
-
2.  Records harvested by MJ CONTENTdm module (newer version harvests)
+
#Records harvested by MJ CONTENTdm module (newer version harvests)
-
3:  Records displayed in Drupal using MJ CONTENTdm module
+
#Records displayed in Drupal using MJ CONTENTdm module
-
4.  Apache Solr does custom searches (Curtis has committed to having it running this month)
+
#Apache Solr does custom searches (Curtis has committed to having it running this month)
Notes:
Notes:
-
1.  Mark Jordan's module harvests only selected fields.  The modules will have to be changed to harvest other custom fields.  This can be done.  If you need help, he should be able to give you some advice.
+
#Mark Jordan's module harvests only selected fields.  The modules will have to be changed to harvest other custom fields.  This can be done.  If you need help, he should be able to give you some advice.
-
2.  There are Apache Solr modules out there that should do most of the things we need
+
#There are Apache Solr modules out there that should do most of the things we need
Enhancements:
Enhancements:
-
1.  Google mapping.  The harvested data should work with the GMAP module.. mapped fields may have to be mapped to the appropriate gmap fields.
+
#Google mapping.  The harvested data should work with the GMAP module.. mapped fields may have to be mapped to the appropriate gmap fields.
-
2.  Biblio module.  This should be considered a "stage 2" wish, but it may help to keep it in mind when developing (and especially when mapping fields).  Also, if it is possible to implement right away, that would be great (and it may be simple to do).
+
#Biblio module.  This should be considered a "stage 2" wish, but it may help to keep it in mind when developing (and especially when mapping fields).  Also, if it is possible to implement right away, that would be great (and it may be simple to do).

Revision as of 21:01, 14 January 2011

Here are the basic requirements:

  1. Records stored in CONTENTdm
  2. Records displayed in Drupal
  3. Custom search (synonym and fuzzy)

Suggested solution

  1. Records uploaded to CONTENTdm
  2. Records harvested by MJ CONTENTdm module (newer version harvests)
  3. Records displayed in Drupal using MJ CONTENTdm module
  4. Apache Solr does custom searches (Curtis has committed to having it running this month)

Notes:

  1. Mark Jordan's module harvests only selected fields. The modules will have to be changed to harvest other custom fields. This can be done. If you need help, he should be able to give you some advice.
  2. There are Apache Solr modules out there that should do most of the things we need

Enhancements:

  1. Google mapping. The harvested data should work with the GMAP module.. mapped fields may have to be mapped to the appropriate gmap fields.
  2. Biblio module. This should be considered a "stage 2" wish, but it may help to keep it in mind when developing (and especially when mapping fields). Also, if it is possible to implement right away, that would be great (and it may be simple to do).
Personal tools