Re: [CODE4LIB] GRAP: The granular restricted access problem
Issues related to provenance and access control are of great practical importance to the intelligence and defense communities, as well as to the financial sector. There are multiple regions in the problem space that have been explored and for which COTS/GOTS solutions are available. One approach that might work for you is Role Based Access Control, or RBAC. There is a nice introduction to the subject area available at NIST - see http://csrc.nist.gov/groups/SNS/rbac/ I keep wanting to build a sandwich form factor data scanner capable of reading private keys and other PIV data laser-etched onto thin strips of pig, thus implementing Roll Based Access Control using BACACs. Maybe I ought to run the idea past the guys at Fort Meat. Simon On Nov 2, 2011 11:36 PM, "William Denton" wrote: > Some of us at work were talking about a problem the archivist and other > digitizing people have: showing particular digitized objects to particular > people with particular restrictions. We called it GRAP: the granular > restricted access problem. > > Here's the archivist's description. If you also had this problem and > found a solution, we'd love to know. > > # - begin GRAP > > We are generating lots of digital assets (TIFFs of historical photographs, > WAVs of sound recordings and oral histories, etc.) not only in the course > of our regular digitization-for-access activities but also as a result of > researcher requests and requests through Accessibility Services. > > We have a institutional digital repository (DSpace) that works well as a > mass distribution tool, but as with most primary sources there are often > additional restrictions on access based on copyright, donor permissions, > third party privacy issues and other legislation. We are struggling to > find ways of promoting these resources that have additional access > restrictions. > > What we want: > > A system of storing and organizing all digitized materials in one place so > that everyone (librarians, archivists, technicians, IT, scholars, faculty, > students) can find them. > > A means of managing and tracking all these objects that will allow: > > - the creation of unique identifiers (to generate statistical metrics, > track chains of custody, access etc.) > - quick and easy updating > - access controls, possibly with time limits, for all material (X to the > public, Y to this person, Z to students in HUM 101 for one week) > - seamless streaming of audio and video (with access controls) > > # - end GRAP > > Any suggestions welcome. I'll pass along and report back. > > Thanks, > > Bill > -- > William Denton > Toronto, Canada > http://www.miskatonic.org/ >
Re: [CODE4LIB] C4L t-shirt design time
The previous years designs are here: 2011: http://wiki.code4lib.org/index.php/Image:Option4.jpg 2010: http://wiki.code4lib.org/index.php/Image:Code4lib2010_P-Hochstenbach.png 2009: http://code4lib.org/node/273 (has links to older years) -Esme -- Esme Cowles "I went down to my old neighborhood ... and the pool hall I loved as a kid is now a 7-Eleven." -- Social Distortion, Story of My Life On 11/3/2011, at 9:13 AM, Bohyun Kim wrote: > Where can we see the designs for the previous ones? Supposing that they are > online? > > ~Bohyun > > -Original Message- > From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Ann > Lally > Sent: Wednesday, November 02, 2011 6:23 PM > To: CODE4LIB@LISTSERV.ND.EDU > Subject: [CODE4LIB] C4L t-shirt design time > > Hi all, > > I'm getting started on the T-shirt wrangling a bit early this year, so > without further ado... > > Thank you Michael Durbin for the following text which I shamelessly cut and > paste from last year's announcement. > > It's time to submit designs for the Code4Lib 2012 conference T-shirt! > Your design should somehow capture the awesomeness of the code4lib community > and be something you'd be proud to wear. > > The design submissions are for the front of the shirt and may be as large as > 11" by 15". > > Keep in mind that these will be printed in one color on a shirt of another > color, so please make your design accordingly. > > The vendor indicated that they preferred Adobe Illustrator or EPS formatted > files, though we can convert other formats. Please send submissions to me > (e-mail address below) by Monday November 21st, at which point they'll be > posted for your review and voting [probably after the Thanksgiving holiday > here in the U.S.] > > > -- > Ann Lally > Head, Digital Initiatives > University of Washington Libraries > alally_at_uw.edu
Re: [CODE4LIB] GRAP: The granular restricted access problem
We have the exact same problem here. We've recently decided to go with Islandora[1] for digital asset management, and DiscoveryGarden[2] told us they can set up Islandora to provide that kind of granular access. It will be several months at best until we get around to implementing that stage of the project, though, so I can't yet tell you how "quick and easy" it is in practice. Julia [1] http://islandora.ca/ [2]http://discoverygarden.ca/ * Julia Bauder Data Services Librarian Interim Director of the Data Analysis and Social Inquiry Lab (DASIL) Grinnell College Libraries Sixth Ave. Grinnell, IA 50112 641-269-4431 On Wed, Nov 2, 2011 at 10:36 PM, William Denton wrote: > Some of us at work were talking about a problem the archivist and other > digitizing people have: showing particular digitized objects to particular > people with particular restrictions. We called it GRAP: the granular > restricted access problem. > > Here's the archivist's description. If you also had this problem and > found a solution, we'd love to know. > > # - begin GRAP > > We are generating lots of digital assets (TIFFs of historical photographs, > WAVs of sound recordings and oral histories, etc.) not only in the course > of our regular digitization-for-access activities but also as a result of > researcher requests and requests through Accessibility Services. > > We have a institutional digital repository (DSpace) that works well as a > mass distribution tool, but as with most primary sources there are often > additional restrictions on access based on copyright, donor permissions, > third party privacy issues and other legislation. We are struggling to > find ways of promoting these resources that have additional access > restrictions. > > What we want: > > A system of storing and organizing all digitized materials in one place so > that everyone (librarians, archivists, technicians, IT, scholars, faculty, > students) can find them. > > A means of managing and tracking all these objects that will allow: > > - the creation of unique identifiers (to generate statistical metrics, > track chains of custody, access etc.) > - quick and easy updating > - access controls, possibly with time limits, for all material (X to the > public, Y to this person, Z to students in HUM 101 for one week) > - seamless streaming of audio and video (with access controls) > > # - end GRAP > > Any suggestions welcome. I'll pass along and report back. > > Thanks, > > Bill > -- > William Denton > Toronto, Canada > http://www.miskatonic.org/ >
[CODE4LIB] Job Posting: Senior Systems Librarian, Brandeis University, Waltham MA
Senior Systems Librarian Brandeis University, a private research university in the metropolitan Boston area, seeks an experienced, innovative and service-oriented Senior Systems Librarian to serve as an integral member of the library systems team. The primary responsibility of the position is to implement, develop and support complex software systems for the Libraries. The Senior Systems Librarian will serve as the primary administrator and support person for a variety of commercial and open source systems, and develop, maintain and enhance integration between library systems, other campus systems and cloud services. Responsibilities include: * Providing administration, support and enhancement of a variety of library systems, including but not limited to the integrated library system, link resolver, proxy server, federated search system, archives management system, interlibrary loan management system * Developing integration between library systems, other campus systems and cloud services * Providing project management and oversight of technical operations, in partnership with the Manager of Library Systems * Performing ad-hoc scripting, report writing and data munging Qualifications include: * Master's degree in library science or related field and 3-5 years demonstrated experience administering library systems, preferably in an academic setting. Relevant work experience may be substituted for some of the required education. * Strong knowledge of Linux and Windows operating systems, Apache, and relational databases * Proficiency with HTML and XML, Javascript, Perl (or PHP), SQL * Experience maintaining and supporting library automated systems and resources, especially including, but not limited to, Aleph, Metalib, SFX, EZProxy, ILLiad. * Strong interpersonal and communication skills ; ability to establish good working relationships with colleagues and vendors * Strong analytical, technical and troubleshooting skills for complex applications The successful candidate will be flexible, creative, and enthusiastic, with a strong interest in exploring and implementing emerging technologies and innovative services. S/he will have a demonstrated ability to work collaboratively and possess a strong service commitment, with a demonstrated ability to plan, coordinate and carry out complex projects. Preference will be given to candidates who demonstrate the ability to operate and maintain library systems, knowledge of current issues and trends in library technology, knowledge of contemporary web design and development, and project management abilities. How to apply: Submit cover letter and resume as a single document at http://www.brandeis.edu/humanresources/jobs/external.html Job ID 520056 Closing Statement: Brandeis University operates under an affirmative action plan and encourages minorities, women, disabled individuals, and eligible veterans to apply. It is the policy of the University not to discriminate against any applicant or employee on the basis of race, ancestry, color, religion, sex, sexual orientation, age, genetic information, national origin, disability, veteran status, or on the basis of any other legally protected category.
Re: [CODE4LIB] GRAP: The granular restricted access problem
On 3 November 2011, Mike Taylor wrote: In the mean time, it's hard to get excited about building software to *restrict* access to materials, when what we all really want to do is *improve* access. I know what you mean, but with archival material, there are lots of cases where setting up restricted access actually is an improvement: without it, there'd be no (online) access at all; the person would have to physically come to the archive and show identification to view the diary that won't be open to the public for 50 years. Bill -- William Denton Toronto, Canada http://www.miskatonic.org/
Re: [CODE4LIB] C4L t-shirt design time
Where can we see the designs for the previous ones? Supposing that they are online? ~Bohyun -Original Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Ann Lally Sent: Wednesday, November 02, 2011 6:23 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: [CODE4LIB] C4L t-shirt design time Hi all, I'm getting started on the T-shirt wrangling a bit early this year, so without further ado... Thank you Michael Durbin for the following text which I shamelessly cut and paste from last year's announcement. It's time to submit designs for the Code4Lib 2012 conference T-shirt! Your design should somehow capture the awesomeness of the code4lib community and be something you'd be proud to wear. The design submissions are for the front of the shirt and may be as large as 11" by 15". Keep in mind that these will be printed in one color on a shirt of another color, so please make your design accordingly. The vendor indicated that they preferred Adobe Illustrator or EPS formatted files, though we can convert other formats. Please send submissions to me (e-mail address below) by Monday November 21st, at which point they'll be posted for your review and voting [probably after the Thanksgiving holiday here in the U.S.] -- Ann Lally Head, Digital Initiatives University of Washington Libraries alally_at_uw.edu
Re: [CODE4LIB] GRAP: The granular restricted access problem
Not the kind of suggestion you're looking for, I know, but as a broader philosophical point ... I wonder how much of the infrastructure we're building now to manage access rights, including dark achives like CLOCKSS, is going to end up looking rather quaint and old-fashioned as the progress towards an Everything Is Open world accelerates. Of course, "Everything" is an exaggeration, there will always be *some* restricted materials, but we're already seeing a strong trend towards author-pays open access in scholarly publishing, and towards musicians not trying to limit access to their music, but using it as an advertisement, and both trends seem to be accelerating. I guess the truth is that none of us knows where all this is going to end up. In the mean time, it's hard to get excited about building software to *restrict* access to materials, when what we all really want to do is *improve* access. -- Mike. On 3 November 2011 03:36, William Denton wrote: > Some of us at work were talking about a problem the archivist and other > digitizing people have: showing particular digitized objects to particular > people with particular restrictions. We called it GRAP: the granular > restricted access problem. > > Here's the archivist's description. If you also had this problem and found > a solution, we'd love to know. > > # - begin GRAP > > We are generating lots of digital assets (TIFFs of historical photographs, > WAVs of sound recordings and oral histories, etc.) not only in the course of > our regular digitization-for-access activities but also as a result of > researcher requests and requests through Accessibility Services. > > We have a institutional digital repository (DSpace) that works well as a > mass distribution tool, but as with most primary sources there are often > additional restrictions on access based on copyright, donor permissions, > third party privacy issues and other legislation. We are struggling to find > ways of promoting these resources that have additional access restrictions. > > What we want: > > A system of storing and organizing all digitized materials in one place so > that everyone (librarians, archivists, technicians, IT, scholars, faculty, > students) can find them. > > A means of managing and tracking all these objects that will allow: > > - the creation of unique identifiers (to generate statistical metrics, track > chains of custody, access etc.) > - quick and easy updating > - access controls, possibly with time limits, for all material (X to the > public, Y to this person, Z to students in HUM 101 for one week) > - seamless streaming of audio and video (with access controls) > > # - end GRAP > > Any suggestions welcome. I'll pass along and report back. > > Thanks, > > Bill > -- > William Denton > Toronto, Canada > http://www.miskatonic.org/ > >
