Community
Participate
Working Groups
Created attachment 79239 [details] Screen capture fo the UI. Although we have extensive project metadata for EMF already http://www.eclipse.org/modeling/emf/project-info/project-info.xml I have to reenter it again using a very tedious UI and I can't delegate that task to anyone else. A nice form for entering all the information (with examples) would make life a lot simpler. Also, an action to import the information from the existing project-info.xml would be a lot less work, and given that the portal is supposed to make life easier (and it's generally been very good!) in this case we seem to be falling short on that goal. We have less extensive information for EMFT: http://www.eclipse.org/modeling/emft/project-info/project-info.xml 1) Is it reasonable that I should be able to delegate the task of updating this information? 2) Can we improve the UI so that I don't need to cycle through 26 separate edit/update cycles (times 2) to update this information? 3) Can we see a summary of all the data somehow?
Ed, Any informatio in the Project-Info.xml files for each project were imported into the database. So you shouldnt have to enter all the data again. I do agree that the portal component needs example data etc. Check out bug Bug 204011, not sure if this would be considered a duplicate of that.
Would it be possible to pop this app as a separate window (instead of trying to embed it in the portal UI) so that you could have 26 rows and 2+ columns for the data entry? Submitting such a form would save its data and present it back to the use so they could do subsequent changes, etc. If you want to get fancy w/ ajax, by all means... but really all you need is a sea of these: <input type="text" name="fieldName" value="<?php echo $_GET["fieldName"]; ?>"/> I guess you could model it on this very form. Data is submitted and the UI refreshes with the new contents from the database (eg., for Product, Component, CC, Summary...)
Yeah I have to agree... I went in to update the Phoenix data and found it laborious.
(In reply to comment #0) > I have to reenter it again Really? That's not good. Karl claimed he imported all the project-info.xml files into the database already. I was going to mark this as a duplicate, but I will leave it open for Karl to fix the import problem when he returns from his trip. > 1) Is it reasonable .. > 2) Can we improve ... > 3) Can we see a summary ... Yes. See bug 204011.
(In reply to comment #4) > (In reply to comment #0) > > I have to reenter it again > Really? That's not good. Karl claimed he imported all the project-info.xml Is it possible that the www/emf/project-info/project-info.xml file was imported instead of www/modeling/emf/project-info/project-info.xml ? Or... were we non-conforming to the schema?
Karl, please take a look at this - perhaps your script imported the wrong file?
Changing title to what the bug has become.
(In reply to comment #4) > (In reply to comment #0) > > I have to reenter it again > > Really? That's not good. Karl claimed he imported all the project-info.xml > files into the database already. I was going to mark this as a duplicate, but I > will leave it open for Karl to fix the import problem when he returns from his > trip. I guess I'm taken aback that the interface was considered so bad. I thought it was a major improvement over hand-editing XML files. Either way Ward, and Gabe fixed that now. Alright I have to admit that all this moving around of EMF and the relationship between EMF and EMFT is still confusing me. I have no idea what's right or not right, and there are several project-info.xml files out there with data in them. I believe you need the data for modeling.emf, correct? I actually did import a bunch of data for EMF and/or EMFT. Proving that it is live, this page uses that data: http://www.eclipse.org/projects/ And so does this page: http://www.eclipse.org/projects/timeline/ They wouldn't be populated with modeling.emf data if it wasn't imported. Here's what is there: +---------------+----------------+----------------------+ | ProjectInfoID | ProjectID | MainKey | +---------------+----------------+----------------------+ | 2378 | modeling.emf | summaryurl | | 2379 | modeling.emf | gettingstartedurl | | 2380 | modeling.emf | projectshortname | | 2381 | modeling.emf | cvs | | 2382 | modeling.emf | cvs | | 2383 | modeling.emf | cvs | | 2384 | modeling.emf | cvs | | 2385 | modeling.emf | cvs | | 2386 | modeling.emf | cvs | | 2387 | modeling.emf | cvs | | 2388 | modeling.emf | blog | | 2389 | modeling.emf | blog | | 2390 | modeling.emf | articleurl | | 2391 | modeling.emf | projectname | | 2392 | modeling.emf | paragraphurl | | 2393 | modeling.emf | descriptionurl | | 2394 | modeling.emf | contributingurl | | 2395 | modeling.emf | bugzilla | | 2396 | modeling.emf | newsgroup | | 2397 | modeling.emf | projectplanurl | | 2398 | modeling.emf | wikiurl | | 2399 | modeling.emf | teamurl | | 2400 | modeling.emf | iplogurl | | 2401 | modeling.emf | release | | 2402 | modeling.emf | release | | 2403 | modeling.emf | release | | 2405 | modeling.emf | release | | 2406 | modeling.emf | release | | 2407 | modeling.emf | release | | 2408 | modeling.emf | release | | 2409 | modeling.emf | release | | 2410 | modeling.emf | mailinglist | | 2411 | modeling.emf | newsgroup | | 2412 | modeling.emf | release | | 2413 | modeling.emf | release | | 2414 | modeling.emf | release | | 2415 | modeling.emf | release | | 2416 | modeling.emf | release | | 2419 | modeling.emf | mailinglist | | 2420 | modeling.emf | release | | 2421 | modeling.emf | newsgroup | | 2422 | modeling.emf | release | | 2423 | modeling.emf | release | | 2424 | modeling.emf | mailinglist | | 2425 | modeling.emf | release | | 2426 | modeling.emf | release | | 2427 | modeling.emf | release | | 2428 | modeling.emf | release | | 2429 | modeling.emf | release | | 2430 | modeling.emf | release | | 2431 | modeling.emf | release | | 2432 | modeling.emf | release | | 3542 | modeling.emf | categories | | 3547 | technology.emf | categories | | 3710 | modeling.emf | downloadsurl | | 3801 | modeling.emf | projecturl | | 3837 | tools.emf | documentationurl | | 3862 | tools.emf | wikiurl | +---------------+----------------+----------------------+ +---------------+---------------+----------------------+ | ProjectInfoID | ProjectID | MainKey | +---------------+---------------+----------------------+ | 2807 | modeling.emft | paragraphurl | | 2808 | modeling.emft | descriptionurl | | 2809 | modeling.emft | bugzilla | | 2810 | modeling.emft | summaryurl | | 2811 | modeling.emft | projectplanurl | | 2812 | modeling.emft | gettingstartedurl | | 2813 | modeling.emft | iplogurl | | 2814 | modeling.emft | cvs | | 2815 | modeling.emft | cvs | | 2816 | modeling.emft | release | | 2818 | modeling.emft | newsgroup | | 2819 | modeling.emft | mailinglist | | 3622 | modeling.emft | projectname | | 3713 | modeling.emft | downloadsurl | | 3804 | modeling.emft | projecturl | +---------------+---------------+----------------------+ If that's not correct, or you're somehow not seeing it, or the project name is just wrong, please tell me what it should say and I'll take care of it right away.
Closing WORKSFORME. Re-open if something is still not correct.
Released
