VERY INTERESTED!!!
We would like to have it yesterday. Right now, we are building a specialized directory with relatively few links, but a lot of information for each one. We need to have a comprehensive resource completely in place before we launch it publicly -- but progress has been slow, taking a lot longer than expected.
The LinksSQL editing interface just isn't suitable for intensive work involving many editors ... to keep everyone onboard, we stopped using the conventional LinksSQL user/editor interface, and we are now creating the database using the DBMan flatfile script. When it is finished, we will convert to MySQL tables. It works -- but only just.
The main concept is separation of the database from all other aspects of LinksSQL, and we would like to be able to continue like this after the directory goes live.
Features we would like to see:
---- Using remote connection (which we can do)
* Multiple editors working offline, with admin controls on where they can edit. That implies an editor table containing permissions for each individual.
* Admin review of what individual editors have done. Rollback not necessary, but some kind of tracking would be very useful.
---- Without a remote connection
* Have one or more editors working totally offline, creating data files that can be merged into the main database by admin. Submission could be by file upload or by email to admin. Implies the ability to check for redundancy and inconsistency in the data before merging.
We are currently set up at pair Networks, who provide MySQL databases with three passwords -- readonly, writeonly, readwrite -- plus the option of remote connection (though we would be reluctant to allow remote connection after the inital stages of the project).
We would like to have it yesterday. Right now, we are building a specialized directory with relatively few links, but a lot of information for each one. We need to have a comprehensive resource completely in place before we launch it publicly -- but progress has been slow, taking a lot longer than expected.
The LinksSQL editing interface just isn't suitable for intensive work involving many editors ... to keep everyone onboard, we stopped using the conventional LinksSQL user/editor interface, and we are now creating the database using the DBMan flatfile script. When it is finished, we will convert to MySQL tables. It works -- but only just.
The main concept is separation of the database from all other aspects of LinksSQL, and we would like to be able to continue like this after the directory goes live.
Features we would like to see:
---- Using remote connection (which we can do)
* Multiple editors working offline, with admin controls on where they can edit. That implies an editor table containing permissions for each individual.
* Admin review of what individual editors have done. Rollback not necessary, but some kind of tracking would be very useful.
---- Without a remote connection
* Have one or more editors working totally offline, creating data files that can be merged into the main database by admin. Submission could be by file upload or by email to admin. Implies the ability to check for redundancy and inconsistency in the data before merging.
We are currently set up at pair Networks, who provide MySQL databases with three passwords -- readonly, writeonly, readwrite -- plus the option of remote connection (though we would be reluctant to allow remote connection after the inital stages of the project).
