|
|
|
[
Permlink
| « Hide
]
Joshua Ryan - 30-Nov-2006 01:06
Would the placementId be good enough context for the REF field?
Should un successful updates be logged? or just successful actions?
I do not know of any implementation details of the News Tool but, in my opinion, the REF field should have a syntax similar to the following (to match other tools REFs):
/news/site/[SITE_ID]/feed/[FEED_ID] You can view what others are logging in SAKAI_EVENT table. Example of a resource file REF: /content/group/b0f42760-cc3a-4938-00ea-dbf4208bccbd/NCRMResearchMethodsTypology.pdf Probably unsuccessful updates shouldn't be logged (I think other tools don't do it). nuno. A news tool only has a title, a url and a placementId. The url and title can be changed during any update. Is it more important for the REF to be consistent or descriptive?
/news/site/[SITE_ID]/feed/[placementId] Using the plancementId would stay the same for the life of the tool instance, the url could be used instead and would be more descriptive as to what content the user actually saw, but it would get ugly when/if the news adds support for aggregation of multiple feeds in one tool (possibly 2.4). Hi Joshua,
I now understand your problem. Data is kept on the tool registry (feed URL stored under 'channel-url:'). Also, feed url is not associated with any kind of identifier and the url is not appropriate for the REF field. I do not have better ideas! Perhaps just change your proposed REF to have 'placement' instead of 'feed' as it could lead to confusion?? Like: /news/site/[SITE_ID]/placement/[placementId] (just a suggestion) Thanks, nuno |
|||||||||||||||||||||||||||||||||||||||||||||||||||