Web Services - Add Custom Fields - Revision history

Bleber: /* Notes/Comments */

2011-01-07T19:33:58Z

Notes/Comments

← Older revision		Revision as of 19:33, 7 January 2011
Line 18:		Line 18:

	== Notes/Comments ==		== Notes/Comments ==
	* For permissions: it seems to me that anyone with only "view" access should at most be able to create private custom fields, i.e., fields viewable only by the creator. It seems like it should require "edit" access to create publicly-viewable custom fields.		* For permissions: it seems to me that anyone with only "view" access should at most be able to create private custom fields, i.e., fields viewable only by the creator. It seems like it should require "edit" access to create publicly-viewable custom fields. -- Geoff Gordon, 1/6/2011

			* It seems like there should be an error when someone tries to add a custom field value for a key that doesn't exist, and at least a warning when someone tries to delete an object (e.g., a KC) which has custom fields attached. In the latter case, telling the system to delete the KC anyway should presumably lead to deletion of the corresponding custom field values. -- Geoff Gordon, 1/6/2011

	* It seems like there should be an error when someone tries to add a custom field value for a key that doesn't exist, and at least a warning when someone tries to delete an object (e.g., a KC) which has custom fields attached. In the latter case, telling the system to delete the KC anyway should presumably lead to deletion of the corresponding custom field values.

	~~-- Geoff Gordon, 1/6/2011~~

	----		----

Bleber: /* Notes/Comments */

2011-01-07T19:04:46Z

Notes/Comments

← Older revision		Revision as of 19:04, 7 January 2011
Line 18:		Line 18:

	== Notes/Comments ==		== Notes/Comments ==
	~~''Your feedback here''~~		* For permissions: it seems to me that anyone with only "view" access should at most be able to create private custom fields, i.e., fields viewable only by the creator. It seems like it should require "edit" access to create publicly-viewable custom fields.

			* It seems like there should be an error when someone tries to add a custom field value for a key that doesn't exist, and at least a warning when someone tries to delete an object (e.g., a KC) which has custom fields attached. In the latter case, telling the system to delete the KC anyway should presumably lead to deletion of the corresponding custom field values.

			-- Geoff Gordon, 1/6/2011

	----		----

Bleber: /* We are seeking your feedback on our current design proposal. */

2011-01-06T15:02:13Z

<span style="color:#37567F">We are seeking your feedback on our current design proposal.</span>

← Older revision		Revision as of 15:02, 6 January 2011
Line 8:		Line 8:
	'''Please add your comments by Wed January 19 2011''' (after which we'll be writing low-level requirements)		'''Please add your comments by Wed January 19 2011''' (after which we'll be writing low-level requirements)

	* [[media:WebServicesProposal2011-public.pdf\|Web Services Proposal 2011 (PDF, 827 KB)]] ~~(commenting enabled)~~		* [[media:WebServicesProposal2011-public.pdf\|Web Services Custom Fields Proposal 2011 (PDF, 827 KB)]]

			Feel free to add comments in the document and email it to datashop-help@lists.andrew.cmu.edu, or add comments on this wiki page.

	== User Stories ==		== User Stories ==

Bleber: /* We are seeking your feedback on our current design proposal. */

2011-01-06T15:00:07Z

<span style="color:#37567F">We are seeking your feedback on our current design proposal.</span>

← Older revision		Revision as of 15:00, 6 January 2011
Line 7:		Line 7:

	'''Please add your comments by Wed January 19 2011''' (after which we'll be writing low-level requirements)		'''Please add your comments by Wed January 19 2011''' (after which we'll be writing low-level requirements)

			* [[media:WebServicesProposal2011-public.pdf\|Web Services Proposal 2011 (PDF, 827 KB)]] (commenting enabled)

	== User Stories ==		== User Stories ==

Alida at 22:05, 5 January 2011

2011-01-05T22:05:17Z

← Older revision		Revision as of 22:05, 5 January 2011
Line 7:		Line 7:

	'''Please add your comments by Wed January 19 2011''' (after which we'll be writing low-level requirements)		'''Please add your comments by Wed January 19 2011''' (after which we'll be writing low-level requirements)



	== User Stories ==		== User Stories ==

Bleber: /* Notes/Comments */

2011-01-05T20:48:40Z

Notes/Comments

← Older revision		Revision as of 20:48, 5 January 2011
Line 21:		Line 21:
	----		----
	See on-going [[DataShop 4.x Features]]<br>		See on-going [[DataShop 4.x Features]]<br>
	See unordered [[Collected User Requests]]		See unordered [[Collected User Requests]]<br>
			See [[Web Services]]
	[[Category:Protected]]		[[Category:Protected]]
	[[Category:DataShop]]		[[Category:DataShop]]

Bleber at 20:30, 5 January 2011

2011-01-05T20:30:28Z

← Older revision		Revision as of 20:30, 5 January 2011
Line 17:		Line 17:
	== Notes/Comments ==		== Notes/Comments ==
	''Your feedback here''		''Your feedback here''


			----
			See on-going [[DataShop 4.x Features]]<br>
			See unordered [[Collected User Requests]]
			[[Category:Protected]]
			[[Category:DataShop]]

Bleber at 20:12, 5 January 2011

2011-01-05T20:12:10Z

← Older revision		Revision as of 20:12, 5 January 2011
Line 1:		Line 1:
			'''status:''' pslc member review of design proposal

	== <span style="color:#37567F">We are seeking your feedback on our current design proposal.</span> ==		== <span style="color:#37567F">We are seeking your feedback on our current design proposal.</span> ==
	We've been discussing and designing a new feature for DataShop—the ability to add and modify custom fields for existing data in DataShop. '''We'd like your feedback!''' If you have a moment, take a look at the PDF below, pages 1-9 (the rest is an archive of our discussion that you're also welcome to read). Then send us feedback or add it to this page below.		We've been discussing and designing a new feature for DataShop—the ability to add and modify custom fields for existing data in DataShop. '''We'd like your feedback!''' If you have a moment, take a look at the PDF below, pages 1-9 (the rest is an archive of our discussion that you're also welcome to read). Then send us feedback or add it to this page below.

Bleber: /* Notes/Comments */

2011-01-05T20:04:45Z

Notes/Comments

← Older revision		Revision as of 20:04, 5 January 2011
Line 14:		Line 14:

	== Notes/Comments ==		== Notes/Comments ==
	~~''' Comments on the Proposal for Web Services: Custom Fields '''~~

	''Your feedback here''		''Your feedback here''

Bleber at 20:04, 5 January 2011

2011-01-05T20:04:29Z

← Older revision		Revision as of 20:04, 5 January 2011
Line 1:		Line 1:

	== <span style="color:#37567F">We are seeking your feedback on our current design proposal.</span> ==		== <span style="color:#37567F">We are seeking your feedback on our current design proposal.</span> ==
	We've been discussing and designing a new feature for DataShop—the ability to add and modify custom fields for existing data in DataShop. '''We'd like your feedback!''' If you have a moment, take a look at the PDF below, pages 1-9 (the rest is an archive of our discussion that you're also welcome to read). Then send us feedback or add it to this page below.		We've been discussing and designing a new feature for DataShop—the ability to add and modify custom fields for existing data in DataShop. '''We'd like your feedback!''' If you have a moment, take a look at the PDF below, pages 1-9 (the rest is an archive of our discussion that you're also welcome to read). Then send us feedback or add it to this page below.
Line 12:		Line 11:

	# As a researcher (EDM, M&M, CMDM), I want to retrieve transaction data programmatically and append custom fields to transactions in DataShop so that I can more easily run my models on the data outside of DataShop and put the results back in.		# As a researcher (EDM, M&M, CMDM), I want to retrieve transaction data programmatically and append custom fields to transactions in DataShop so that I can more easily run my models on the data outside of DataShop and put the results back in.
	~~# As a researcher with a machine learning background, I want to retrieve student-step data programmatically so that I can more easily run my analyses on the data without much human intervention.~~
	# As a researcher who has created a custom field for an existing data set, I want to import that new field into the step rollup table so that it is both preserved and available in DataShop tools. - Ryan Baker, 12/15/2008		# As a researcher who has created a custom field for an existing data set, I want to import that new field into the step rollup table so that it is both preserved and available in DataShop tools. - Ryan Baker, 12/15/2008

	== Notes/Comments ==		== Notes/Comments ==
	''' ~~<span style="color:#37567F">~~Comments on the Proposal for Web Services: Custom Fields~~</span>~~ '''		''' Comments on the Proposal for Web Services: Custom Fields '''

	''Your feedback here''		''Your feedback here''