cryptonome / opendms-dot-net Goto Github PK

Currently new resource creation works by making multiple calls to the couchdb 
both receiving and sending information.  Much of these communication sessions 
could be combined using bulk document operations.  This will require our 
transaction system to be expanded to cross document boundaries.

Simple, but needed!

Common.MetaAsset needs to specifically define a collection of types that it 
will support for the value portion of its UserProperties collection.  
Additionally, it needs to check all inputs to UserProperties to ensure the 
value is within the supported types.

It appears settings could be getting loaded from disk each time the static 
variable is accessed.  Basically, both ServerSettings and Settings need 
reworked.  This needs to be made into some sort of legitimate settings 
class/classes/system because the amount of potential settings are expected to 
grow.

In permissions checking, if a user is defined as a superuser, it need not check 
global or resource permissions.  Superusers pass all checks.

Currently, most all logging is only done when an error occurs.  Logging needs 
to be much more liberal since we are now using log4net.

Logger is gross, it has problems when running in the Server.  It needs 
researched to find a better method of implementation.

Currently the project has c-l index the usagerights.  This is pointless.  Thus, 
we need to tell c-l to ignore the usagerights for indexing.  

Robert Newson reminded me of this on Stackoverflow 
(http://stackoverflow.com/questions/7327502/using-couchdb-lucene-how-can-i-index
-an-array-of-objects-not-values).

This needs corrected in: 
OpenDMS.Storage.Providers.CouchDB.Transactions.Processes.Install

Developers that already have the source installed and running need to modify 
their _design/search document accordingly.

No other modifications are required.

What steps will reproduce the problem?
1. Generate a meta asset
2. Reduce the total length of the xml data for the meta asset
3. Old information will trail the termination of the current meta asset xml 
marker.

What is the expected output? What do you see instead?
I expect to see the </MetaAsset> at the end, instead I see the data that had 
previously existed at its same location.

Whenever a groups members (users) are updated that modification needs pushed to 
each user that has been modified.  Thus, if a user is removed from the group, 
the user needs to have that group removed from it.  This also needs to happen 
in the other direction, users to groups.

The Transactions.Transaction.Commit() needs to include indexing on both meta 
and data assets.

Yea, this whole system is gross, it needs to be easier to understand, maintain 
and use.

Currently it is built into the WindowsClient's main window.  The file system 
monitor needs built into its own subsystem.  This does not need to happen 
anytime soon.