Drupal Development - Revision history

Coline at 17:52, 26 May 2011

2011-05-26T17:52:22Z

← Older revision		Revision as of 17:52, 26 May 2011
Line 21:		Line 21:
	*[[views]]		*[[views]]
	*[[colour pallette]]		*[[colour pallette]]
		+	*[[tables]]

Coline at 19:41, 25 May 2011

2011-05-25T19:41:15Z

← Older revision		Revision as of 19:41, 25 May 2011
Line 20:		Line 20:
	*[[modules]]		*[[modules]]
	*[[views]]		*[[views]]
		+	*[[colour pallette]]

Coline at 04:38, 25 April 2011

2011-04-25T04:38:18Z

← Older revision		Revision as of 04:38, 25 April 2011
Line 19:		Line 19:

	*[[modules]]		*[[modules]]
		+	*[[views]]

Coline at 06:04, 24 April 2011

2011-04-24T06:04:35Z

← Older revision		Revision as of 06:04, 24 April 2011
Line 17:		Line 17:
	#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.
	#Biblio module. <del>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).</del>This module should be implemented in phase 1 if possible.		#Biblio module. <del>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).</del>This module should be implemented in phase 1 if possible.
		+
		+	*[[modules]]

Coline at 16:28, 24 February 2011

2011-02-24T16:28:40Z

← Older revision		Revision as of 16:28, 24 February 2011
Line 16:		Line 16:
	Enhancements:		Enhancements:
	#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.
-	#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. <del>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).</del>This module should be implemented in phase 1 if possible.

Coline at 21:03, 14 January 2011

2011-01-14T21:03:33Z

← Older revision		Revision as of 21:03, 14 January 2011
Line 8:		Line 8:
	#Records harvested by MJ CONTENTdm module (newer version harvests)		#Records harvested by MJ CONTENTdm module (newer version harvests)
	#Records displayed in Drupal using MJ CONTENTdm module		#Records displayed in Drupal using MJ CONTENTdm module
-	#Apache Solr does custom searches (<del>Curtis has committed to having it running this month</del>) Curtis did not complete, but Bill says that other modules may suffice	+	#Apache Solr does custom searches (<del>Curtis has committed to having it running this month</del>) Curtis did not complete, but Bill says that other modules may suffice. He is investigating

	Notes:		Notes:

Coline at 21:03, 14 January 2011

2011-01-14T21:03:16Z

← Older revision		Revision as of 21:03, 14 January 2011
Line 8:		Line 8:
	#Records harvested by MJ CONTENTdm module (newer version harvests)		#Records harvested by MJ CONTENTdm module (newer version harvests)
	#Records displayed in Drupal using MJ CONTENTdm module		#Records displayed in Drupal using MJ CONTENTdm module
-	#Apache Solr does custom searches (Curtis has committed to having it running this month)	+	#Apache Solr does custom searches (<del>Curtis has committed to having it running this month</del>) Curtis did not complete, but Bill says that other modules may suffice

	Notes:		Notes:
-	#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.	+	#<del>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.</del>According to Bill it does harvest all fields
	#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

Coline at 21:01, 14 January 2011

2011-01-14T21:01:01Z

← Older revision		Revision as of 21:01, 14 January 2011
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).

Coline at 21:00, 14 January 2011

2011-01-14T21:00:03Z

← Older revision		Revision as of 21:00, 14 January 2011
Line 1:		Line 1:
	Here are the basic requirements:		Here are the basic requirements:
-	1. Records stored in CONTENTdm	+	#Records stored in CONTENTdm
-	2. Records displayed in Drupal	+	#Records displayed in Drupal
-	3. Custom search (synonym and fuzzy)	+	#Custom search (synonym and fuzzy)

	Suggested solution		Suggested solution

Coline: Created page with "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..."

2011-01-14T20:59:04Z

Created page with "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..."

New page

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).