[Dspace-devel] Theme access to external identifiers (DOI, Handle, etc.)
I need to provide an external identifier (DOI if available, Handle if not) to our Theme so that it can cobble up a query to a remote service. o This seems like something generally useful. Would there be others interested in having all of an object's identifiers listed in pageMeta? Then the Theme can pick whichever it likes best. o It's easy enough to enumerate an object's identifiers, but the only way to know what kind of identifier this one is, is to guess based on the class name of the provider. Good luck with that, if the site has built its own provider. Is there some reason why IdentifierProvider should not be extended with a method to return a sort of name for the type of identifiers that it provides? Any suggestions for what should be returned? -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Machines should not be friendly. Machines should be obedient. signature.asc Description: Digital signature -- Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] Theme access to external identifiers (DOI, Handle, etc.)
Never mind. After chatting with pbecker on IRC, I think I can do what I need using the METS document already available to the presentation layer, without hacking the Identifier code. I was concerned about depending on internals of the Identifier code in presentation, but I now think that the generation of the METS decouples those well enough. It's going to take some...*interesting*...XSL-T though, to prioritize identifiers by their content. I think I know where I can find some examples in the themes from which to start. -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Machines should not be friendly. Machines should be obedient. signature.asc Description: Digital signature -- Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] DSpace Dev Mtg Tomorrow @ 20:00 UTC and JIRA Backlog Hour @ 19:00 UTC
All, Tomorrow (Weds, July 23) at 20:00 UTC, we have our weekly DSpace Developers Meeting in the #duraspace IRC channel. To determine your local time, check the world clock: http://www.timeanddate.com/worldclock/fixedtime.html?hour=20min=0sec=0p1=0 The agenda is posted on our Developer meetings page at: https://wiki.duraspace.org/display/DSPACE/Developer+Meetings The notes from last week's meeting are also available off of the Meeting Archives area of that page. As always, all our meetings are public. We welcome any developers or non-developers to attend or just read along with the chat discussions. If you are unable to attend, you can always add your own notes/thoughts on any agenda item to the above wiki page. == JIRA Backlog Hour == The hour prior to our Developers Meeting, we will be holding a JIRA Backlog Hour in #dspace IRC (note that it takes place in #dspace and NOT #duraspace). During this meeting, developers who are available will begin to work together to tackle our backlog of Received tickets/bug reports in JIRA. We'll be looking to do a quick analysis of tickets to help move them along through our workflow. Anyone is welcome to join us (and you are more than welcome to just join mid-meeting as well). It's a great way to learn about how we work together to support DSpace, and also a great way to contribute to DSpace software. Plus, you'll be helping all of us to determine which tickets (old and new) could use extra love attention. Our current JIRA Received backlog is at: https://jira.duraspace.org/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+DS+AND+status+%3D+Received+ORDER+BY+key+ASC%2C+priority+DESC We hope to see you in IRC! Thanks, Tim Donohue Technical Lead for DSpace Project DuraSpace.org -- Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
