My favorites | Sign in
Project Home Wiki Issues Source
READ-ONLY: This project has been archived. For more information see this post.
Search
for
  Advanced search   Search tips   Subscriptions
Issue 1: how to treat suggested markups from the DB DESIGN POINT OF VIEW
1 person starred this issue and may be notified of changes. Back to list
 
Project Member Reported by meengu...@yahoo.co.uk, Jul 23, 2010
the sugegsted mark ups, it is essential, are not to be confused or mixed up with the main markups at any stage. Only when in an offline admin activity i change the status of a mark up, it can be treated as a main mark up.. And also there is a very high possiblity that 50-75% of these marks are either dropped or changed i.e. mark text, version identifucation, title, concept.. everything may change about these markup after approval.. further the num,ber of such markups existing in the database may at any time not be more than 50-100. So since keeping these along with the main mark up table may mean we are building in this functionality of checking on whether somehing is approved or not for all applications..i sugest, we may keep those in separate table instead.. so such extra application specification is.. needed..

Powered by Google Project Hosting