Hi Christophe, > I am back after some time in the country side. > > I discover today the committer meeting transcript. > This was exactly what I expected to happen ;-)
> [16:15] <bradmc> All of that sounds good; are we ready to move on to > community admin? > [16:15] <bollini> I'm expect some comments after that the IRC > transcription will be post to the list > First, I am "Christophe" and not "Dupriez"! I hope meeting all of you in > Göteborg to "break the ice"! > yes you are definitely Christophe for me ;-) look forward to meet you in Goteborg > [4:07pm] bollini: we have received many comments from Dupriez and > documentation about a different approach > > My implemented specs (http://www.windmusic.org/dspace) did not received > any approval by comitters: the reaction was Larry and Andrea starting > the same work! > This is not fully true, as far as I know Larry has started is work exactly when he has opened the discussion about authority, sharing before he's spec and solution proposal... I have read your documentation (very good) and I have send back few comments (to your first emails) but Larry, and now myself, is gone ahead because under strictly customer timeline. This "limit" has been underline by Larry in his first email... > [4:08pm] bollini: but we have not received any codes and (as far as I > know) the Dupriez code works on an old dspace 1.4 or less > > My work is on the basis of DSpace 1.4.2 > the main difficult to update it to the 1.5 could be the change to the browse system > [4:09pm] bollini: with the Larry model and few changes that I have made > we can cover the functional requirements of Dupriez > > I do not see how you may support indexation and retrieval by > translations, synonyms and broader concepts (or precise concepts). > I plan to share these changes next week so that you can check it yourself, anyway in brief I give an opportunitiy to the ChoiseAuthority class to give any translations/synonyms at the time of indexing so to add also them to the index. I also store the exact "authority key" in a separate index to allow precise concepts search. I have not a solution for broader concept at the moment, but I think that we can add this functionality after to have experienced on some real case. > Furthermore, if concepts are prefixed by qualifiers (like the MeSH as > used in Pubmed) and suffixed by quantities (like "top" in PubMed or > instruments quantities in WindMusic), the Larry Model is not enough either. > > [4:10pm] stuartlewis: Excellent - sounds good. Are you going to liaise > with Christophe to check that his functional requirements are met? > [4:10pm] bollini: the only think that remains out is the out-of-box SKOS > "integration" of the Dupriez model > [4:10pm] bollini: no Stuart, I haven't > > Data structures are VERY important, especially this one which will > impact BlackLight integration (my next endeavour: > http://projectblacklight.org/). > They should be discussed before final development and integration, on > the basis of what can be measured on some prototypes. > I agree, we need prototypes for evaluate different approaches > WindMusic is there to test (it is operational from the customer point of > view). It will be demonstrated at DSUG 2009 (Göteborg): in 20 minutes!!! > > I hope that we can check together if the Larry prototype with these last changes will work for your use case > I disagree with the idea of not completing the reflexion on the design > of the data structure. > If we agree on data storage, then contributing code becomes much more > easier. > > For my work, I rejected the idea of Larry because it was not providing > all the functionalities my customer needed > (he wants even more now that he intensively uses the system: support of > reflexive "see also" relations, I think that having in the hand the authority key you can interrogate the authority provider during the item splash page rendering and build as complex as needed inter navigation links > auto-complete based on a key more > sophisticated than just the title...) > The auto-complete behaviors is already pluggable so how (and where) you search the authority is fully customizable > I am not a committer (or a release coordinator). I cannot afford to make > a patch to a running target (1.6 or so) and have it rejected without > discussion. > I wants to have an approval on specs and then on data structures and > then on software architecture and then on independant contributions. > this could be a too long process (at least for my related projects deadline), I suggest to you to share the code early and don't worry about have it rejected without a discussion, this is not the case we can use your code to full fit requirements again not covered, better understanding your (customer) needs and also improve existing code. > So the main principle I need to make accepted now is below: > > Anywhere some text may be entered as data, one (and eventually more) > "indexing string" may be specified (helped by a menu or an auto-complete > when possible). > This "indexing string" is composed of: > * an optional prefix which precises the ROLE (example: is the following > person acts as an author? a composer? an illustrator?). > I'm not sure about this... could be more appropriate use a different metadata for any role? i.e myschema.contributor.composer, myschema.contributor.illustrator etc... Anyway, I'm thinking to give a chance to the ChoiseAuthority class to give at the search indexer more string that the "authority key" during the indexing process so to allow the store of string as in your examples Andrea > Have a nice day! > > Christophe > > > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Dspace-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/dspace-devel > > > -- Dott. Andrea Bollini Project Manager, IT Architect & Systems Integrator Sezione Servizi per le Biblioteche e l'Editoria Elettronica CILEA, http://www.cilea.it tel. +39 06-59292853 cel. +39 348-8277525 --- Disclaimer: the content of this email is confidential and may be privileged, and it must not be disclosed or copied without the sender's consent. If you have received this message in error, please notify the sender and remove it from your system. The content of this email does not constitute legal advice, nor any responsibility is accepted for loss or damage incurred as a result of acting upon its contents or attachments. The statements and opinions expressed in this email are those of the author and do not necessarily reflect those of the employer. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
