Support in some way non-ajax enabled browsers, and even non-javascript ones. Some way to guess it on the fly (like load first ‘lite’ version and replace it with full one through ajax) maybe?

While possible, (like authorization etc) use static, non-ajax pages. Ajax pages can’t be bookmarked, that’s bad.

Add support for “Forgot your password?” situation

Change the session mechanism from password-in-cookie to something more secure, like server-side session management with temporary identifiers. Needs database support...

Do we need support for different upload data formats (VOtable, CSV, ASCII)?..

Possibility to enter table metadata while table uploading. Useful when table is received from some other catalogue system, and user don’t know how to edit metadata by hand.

Error handling! Inform user whether his file too big or can’t be processed by the system.

Some kind of upload progress indicator, maybe the same rotating throbber as in other requests.

Critically depends on authorization, especially for system catalogs!

Two-level editing - metadata of catalogs (for admin only), and meta-data of tables inside catalogs (admin for system tables, owner for personal ones)

For now, drop the server-side user file storage. Maybe later. No tasks for it right now.

Instead, make a page showing all user-uploaded tables, along with options to upload new or edit/delete old ones.

Possibility to download back uploaded user table? Impossible through current conesearch, needs another backend solution.