LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  August 2011

CODE4LIB August 2011

Subject:

Re: Seeking feedback on database design for an open source software registry

From:

Brice Stacey <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Tue, 9 Aug 2011 12:47:23 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (63 lines)

I'd be curious to know if this project itself would be open source.

Second, I'm intrigued because I've never seen a UML diagram so close before in the wild and it's fascinating to discover the jokes are true (I kid, I kid...). Let's get serious and pull out your Refactoring book by Fowler and turn to page 336... you can "Extract superclass" to get Provider/Institution/Person to inherit from Entity. Then "Merge Hierarchy" to tear it down into a single Entity class and add a self-referencing association for employs. ProviderType should be renamed to Services and be made an association allowing 0..* services. At that point, the DB design is pretty straight forward and the architecture astronauts can come back down to earth.

Seriously though, I think that technically, you might be over thinking this. If you replace Package with Blog, Release with Post, Technology with Tag, Provider/Institution/Person with User, Keep Comment as Comment, and ignore Event for now.... It's just a simple collection of blogs with posts with tags and users that have roles and can leave comments.

Lastly, you may want to look into Drupal's project module. I think that's what they use to run their module directory. It seems like it would be a good starting point and may work out of the box.
 
It's a bold project. The library needs it and it's something no single institution would ever pay to have done, so I'm glad to see there is a grant for it.

Brice Stacey
Digital Library Services
University of Massachusetts Boston
[log in to unmask]
617-287-5921


On 15 July 2011 19:42, Peter Murray <[log in to unmask]> wrote:
> Colleagues --
>
> As part of the Mellon Foundation grant funding the start-up of LYRASIS Technology Services, LTS is establishing a registry to provide in-depth comparative, evaluative, and version information about open source products.  This registry will be free for viewing and editing (all libraries, not just LYRASIS members, and any provider offering services for open source software in libraries).  Drupal will be the underlying content system, and it will be hosted by LYRASIS.
>
> I'm seeking input on a data model that is intended to answer these questions:
>
>        * What open source options exist to meet a particular need of my library?
>        * What are the strengths and weaknesses of an open source package?
>        * My library has developers with skills in specific technologies. What open source packages mesh well with the skills my library has in-house?
>        * Where can my library go to get training, documentation, hosting, and/or contract software development for a specific open source package?
>        * Are any peers using this open source software?
>        * Where is there more information about this open source software package?
>
> The E-R diagram and narrative surrounding it are on the Code4Lib wiki:
>
>  http://wiki.code4lib.org/index.php/Registry_E-R_Diagram
>
> Comments on the data model can be made as changes to the wiki document, replies posted here, or e-mail sent directly to me.  In addition to comments on the data model, I'm particularly interested in answers to these questions (also listed at the bottom of the wiki page):
>
>  1. The model does not provide for a relationship between a person and a software package. Would such a relationship be useful? E.g., individuals self-identifying as affiliated with an open source software package.
>
>  2. The initial planning process did not account for the inclusion of packages that were not themselves end products. Should code libraries and support programs be included as packages in the registry? The model could conceivably be adjusted in two ways to account for this. The simplest would only require the addition of new PackageType enumerations (e.g. "code library"); this would not allow for searching of packages that use code libraries (e.g., answering the question "What repositories use the djatoka JPEG2000 viewer system?") Another simple change would be to add "code library" to the TechType enumeration; the code library would not have the benefit of links to other relationships and entities.  A more complicated change would do both but there would be no relationship between the code library as a Package and as a Technology.  Are there better ways to add code libraries to the model?
>
>  3. Some who have reviewed the concept for the registry suggested other attributes. Should these be added? (And what is missing?)
>                * Package - Translations
>                * Package - Intended audience (e.g. developers, patrons/desktop, patrons/web, library-staff/desktop, library-staff/web)
>                * Version - Code maturity (e.g., alpha, beta, release candidate, formal release)
>
>  4. To answer the question "Are any peers using this open source software?" is it necessary to have an enumeration of library types? Public library, school library, university library, community college library, special library, museum (others?)
>
>  5. Is the location of Institutions and Providers desired? One reason it might be desirable is to do a geography-based search (e.g. training providers within a 60-mile radius).
>
>
> Feel free to add to the list of questions.  I'm looking forward to your thoughts.
>
>
> Peter
> --
> Peter Murray         [log in to unmask]        tel:+1-678-235-2955
> Ass't Director, Technology Services Development   http://dltj.org/about/
> LYRASIS   --    Great Libraries. Strong Communities. Innovative Answers.
> The Disruptive Library Technology Jester                http://dltj.org/
> Attrib-Noncomm-Share   http://creativecommons.org/licenses/by-nc-sa/2.5/
>
>

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager