Re: [CODE4LIB] Metadata
+1 # everything is data, context makes it meta On Feb 15, 2012, at 10:29 PM, Simon Spero wrote: I have had several theoretical changes of opinion on this question, and have come to the considered opinion that there is no principled *essential* difference between Metadata and Data. It all depends on the context/theory/background assumptions to which the data is being applied. The property of Data being meta is entirely use sensitive. The property of being information may depend upon the existence of metadata referring to the data. For example, it is labeling of an antelope in a zoo as an antelope that turns an ungulate into a document; data measured from this beast gives us evidence about what an antelope is like. The label number of the beast, as well as the date of capture and other provenance, are clearly metadata in this case, and provide the context for interpreting the data as information, and for assessing the degree of justification we have for treating this information as knowledge. However, in other cases, the metadata may serve as data for other studies, with no reference to our four legged friend. Suppose we are doing a study on the rate of differently labeled specimen acquisition in zoos across Europe over the course of the 19th and 20th centuries. In this situation, what was metadata has become our primary data; *our* metadata relates to the provenance of the descriptions. Metadata embedded by a smart sensor package included in the same persuade as the data gathered as part of an observation run is essential to the interpretation of that data as information. However, it is not the primary data itself; it is the context. Radar data from early JSTARS platforms was severely downgraded by rain between the platform and the ground; the information provided needs context about climate conditions in order to determine the actual amount of information obtained when fusing that information with other sensor systems. However, the climate readings are not part of the radar data itself. So, to sum up, it depends; Further Research Is Needed; one man's Meta is another man's Poisson. Simon On Feb 14, 2012 9:59 AM, Michael Hopwood mich...@editeur.org wrote: Having done research, and now working in a very varied metadata role, I don't quite understand this discussion about data that is or isn't metadata. Scientific data is a great example of structured data, but it's not impossible to distinguish it from metadata purely describing a dataset. However, if you have scientific research data created during the experiments, even if it's operational, it's clearly part of the data. This doesn't mean there can't be metadata describing *that data*. Just because it's not glamorous data doesn't mean it's not essential to the scientific process. Similarly, just being about mundane or procedural things doesn't make data into metadata...! You're absolutely right, the contextual information is certainly part of the experimental outcome in this example; otherwise it would be abstract data such as one might use in a textbook example. Metadata would describe the dataset itself, not the scientific research. There's always a certain ambiguity involved in identifying the data as distinct from the metadata, and it's a false dichotomy to suggest metadata is not useful at all for the domain expert. It's contextual, and the definition is always at least partly based on your use case for the data and its description. -Original Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Nate Vack Sent: 14 February 2012 14:45 To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Metadata On Tue, Feb 14, 2012 at 1:22 AM, Graham Triggs grahamtri...@gmail.com wrote: That's an interesting distinction though. Do you need all that data in order to make sense of the results? You don't [necessarily] need to know who conducted some research, or when they conducted it in order to analyse and make sense of the data. In the context of having the data, this other information becomes irrelevant in terms of understanding what that data says. It is *essential* to understanding what the data says. Perhaps you find out your sensor was on the fritz during a time period -- you need to be able to know what datasets are suspect. Maybe the blood pressure effect you're looking at is mediated by circadian rhythms, and hence, times of day. Not all of your data is necessary in every analysis, but a bunch of blood pressure measurements in the absence of contextual information is universally useless. The metadata is part of the data. -n
Re: [CODE4LIB] Metadata
(Pssst: Does it matter if you call it data and I call it metadata?) Sent from my Verizon Wireless Phone -Original message- From: Esmé Cowles escow...@ucsd.edu To: CODE4LIB@listserv.nd.edu Sent: Thu, Feb 16, 2012 09:23:07 GMT+00:00 Subject: Re: [CODE4LIB] Metadata +1 # everything is data, context makes it meta On Feb 15, 2012, at 10:29 PM, Simon Spero wrote: I have had several theoretical changes of opinion on this question, and have come to the considered opinion that there is no principled *essential* difference between Metadata and Data. It all depends on the context/theory/background assumptions to which the data is being applied. The property of Data being meta is entirely use sensitive. The property of being information may depend upon the existence of metadata referring to the data. For example, it is labeling of an antelope in a zoo as an antelope that turns an ungulate into a document; data measured from this beast gives us evidence about what an antelope is like. The label number of the beast, as well as the date of capture and other provenance, are clearly metadata in this case, and provide the context for interpreting the data as information, and for assessing the degree of justification we have for treating this information as knowledge. However, in other cases, the metadata may serve as data for other studies, with no reference to our four legged friend. Suppose we are doing a study on the rate of differently labeled specimen acquisition in zoos across Europe over the course of the 19th and 20th centuries. In this situation, what was metadata has become our primary data; *our* metadata relates to the provenance of the descriptions. Metadata embedded by a smart sensor package included in the same persuade as the data gathered as part of an observation run is essential to the interpretation of that data as information. However, it is not the primary data itself; it is the context. Radar data from early JSTARS platforms was severely downgraded by rain between the platform and the ground; the information provided needs context about climate conditions in order to determine the actual amount of information obtained when fusing that information with other sensor systems. However, the climate readings are not part of the radar data itself. So, to sum up, it depends; Further Research Is Needed; one man's Meta is another man's Poisson. Simon On Feb 14, 2012 9:59 AM, Michael Hopwood mich...@editeur.org wrote: Having done research, and now working in a very varied metadata role, I don't quite understand this discussion about data that is or isn't metadata. Scientific data is a great example of structured data, but it's not impossible to distinguish it from metadata purely describing a dataset. However, if you have scientific research data created during the experiments, even if it's operational, it's clearly part of the data. This doesn't mean there can't be metadata describing *that data*. Just because it's not glamorous data doesn't mean it's not essential to the scientific process. Similarly, just being about mundane or procedural things doesn't make data into metadata...! You're absolutely right, the contextual information is certainly part of the experimental outcome in this example; otherwise it would be abstract data such as one might use in a textbook example. Metadata would describe the dataset itself, not the scientific research. There's always a certain ambiguity involved in identifying the data as distinct from the metadata, and it's a false dichotomy to suggest metadata is not useful at all for the domain expert. It's contextual, and the definition is always at least partly based on your use case for the data and its description. -Original Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Nate Vack Sent: 14 February 2012 14:45 To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Metadata On Tue, Feb 14, 2012 at 1:22 AM, Graham Triggs grahamtri...@gmail.com wrote: That's an interesting distinction though. Do you need all that data in order to make sense of the results? You don't [necessarily] need to know who conducted some research, or when they conducted it in order to analyse and make sense of the data. In the context of having the data, this other information becomes irrelevant in terms of understanding what that data says. It is *essential* to understanding what the data says. Perhaps you find out your sensor was on the fritz during a time period -- you need to be able to know what datasets are suspect. Maybe the blood pressure effect you're looking at is mediated by circadian rhythms, and hence, times of day. Not all of your data is necessary in every analysis, but a bunch of blood pressure measurements in the absence of contextual information is universally useless. The metadata is part of the data. -n
Re: [CODE4LIB] Metadata
On 16 February 2012 12:13, suzanne.pilsk suzanne.pi...@gmail.com wrote: (Pssst: Does it matter if you call it data and I call it metadata?) Yes. Yes it does. Although possibly not for the reasons you might think I'll give. I think it's really important that developers (and researchers) get out of the mindset that: a) metadata isn't data b) metadata isn't important c) data can't be both metadata and data Because the chances are that it is all important, but in different ways, and has different needs in frequency of use, indexing, etc. Treating everything the same, and in one big bucket, is likely to slow down the processes of indexing, locating, and scanning over possible resources. So there is a need to think about things in terms of what is required for different purposes - what is needed for locating and describing resources, and everything that is required to use those resources. And that may well mean having bits of information that are duplicated in more than one bucket. But what we can't be is scared of identifying that there are different needs and requirements, different scopes of relevant data. Or that users actually have names for these scopes. G
Re: [CODE4LIB] Metadata
Patrick, I wanted to come back to the initial question of sufficient metadata. While I think there have been some good answers given, I did not see any mention about how discoverability on the open Web figures in to how to think about metadata. My response got long, so I posted something to my blog. http://jronallo.github.com/blog/sufficient-metadata-and-the-open-web/ Jason On Fri, Feb 10, 2012 at 3:57 PM, Patrick Berry pbe...@gmail.com wrote: So, one question I forgot to toss out at the Ask Anything session is: When do you know you have enough metadata? You'll know it when you have it, isn't the response I'm looking for. So, I'm sure you're wondering what the context for this question is, and honestly there is none. This is geared towards contentDM or DSpace or Omeka or Millennium. I've seen groups not plan enough for collecting data and I've seen groups that are have been planning so long they forgot what they were supposed to be collecting in the first place. So, I'll just throw that vague question out there and see who wants to take a swing. Thanks, Pat/@pberry
[CODE4LIB] Job Opening: Senior Digital Library Developer, Temple University
The Temple University Library is seeking a creative and energetic individual to fill the newly-created position of Senior Digital Library Developer in the Digital Library Initiatives Department. Reporting to the Head of the Department and working closely with other members of the Digital Library Infrastructure Group, the Senior Digital Library Developer will play a leading role in designing and implementing the overall architecture, workflows, and applications for Temple's digital library services. Duties * Working with open-source applications and toolkits, design and implement a multi-purpose repository infrastructure that supports the ingestion, preservation, and delivery of digital objects, in accordance with the OAIS model, and with attention to TRAC’s recommendations. * Provide specialized front-end interfaces to the repository for both digital object creation and end-user delivery, by using, adapting, and extending open source and commercial applications. * Design and implement efficient pipelines to extract, transform and repurpose metadata and digital objects as needed. * Gather requirements and develop specifications for various aspects of the digital library architecture; work closely with digital object creators and managers to understand their needs. * Test, evaluate, and recommend potential toolkits and applications for inclusion in the repository architecture. * Collaborate with the Library Technology Services Department as well as Campus-wide Computing Services, to ensure proper management and use of mass storage clusters, and proper implementation of security guidelines and authentication/authorization policies. * Maintain digital library architecture, troubleshooting issues whenever they arise. * Maintain awareness of community-wide developments in the realm of digital library software and infrastructure. * As the opportunity arises, contribute to the development of Open Source and Community Source applications. * Write and maintain documentation for overall architecture and code. * May supervise junior programmers (part-time student employees or full-time staff). * Serve on the Digital Library Infrastructure Group. * Perform other duties as assigned. Qualifications Required Education and Experience: BS in Computer Science or related field, and at least two (2) years of relevant experience. An equivalent combination of education and experience may be considered. Required Skills and Abilities: *Demonstrated experience with web-based development in a programming language such as Java or Ruby on Rails. *Demonstrated experience with web-based software integration, for instance using RESTful APIs. *Demonstrated experience with Unix/Linux, including basic administration, shell scripting, device management, working with protocols like NFS, CIFS, and Webdav, and basic data storage management. *Knowledge of current web development standards, including cross-platform compatibility, ADA compliance, and security. *Demonstrated ability to perform effective code testing. *Strong organizational skills, and ability to manage projects involving a small-to-medium staff team. *Strong interpersonal skills and demonstrated ability to work in a collaborative team-based environment. *Excellent oral and written communication skills with demonstrated ability to write clear documentation. *Demonstrated ability to communicate well with non-IT staff. *Demonstrated commitment to providing excellent customer service. Preferred: * Experience with software development in an academic library or higher education setting. * Experience with managing digital object identifiers, delivering digital objects to end users (including Jpeg2000 delivery, page turning viewers, audio/video streaming), and working with authentication and authorization technologies, including LDAP. * Knowledge of XML/XSLT, and a scripting language like PHP. * Experience with metadata extraction, transformation, and repurposing * Familiarity with digital library standards, such as, Dublin Core, MARC, METS, EAD, and OAI-PMH. * Experience with a repository system like Fedora or Dspace. * Familiarity with CONTENTdm and a Web-based Content Management System like Drupal would be a plus. * Experience working with Open Source software; experience with version control, test-driven development, and continuous integration techniques, using tools such as Git and Hudson * Experience managing student workers or full-time staff. * Experience working in an Agile project management environment. About Temple University Temple's federated library system serves an urban research university with over 1,800 full-time faculty and a student body of 36,000 that is among the most diverse in the nation. For more information about Temple and Philadelphia, visit http://www.temple.edu. Temple University is an Affirmative Action/Equal Opportunity Employer with a strong commitment to cultural diversity. To apply: * please go to should go to
[CODE4LIB] Job Opening: Research Programmer, Mobile/Web Apps Developer, UIUC
Research Programmer Mobile/Web Applications Developer Visiting Academic Professional Position University Library University of Illinois at Urbana-Champaign Position Available: This position is available immediately. This is a 100%-time, twelve-month appointment Visiting Academic Professional position. Duties and Responsibilities: The successful candidate will be appointed to support a digital library grant-funded research project being conducted at the Undergraduate Library. The appointee will report to the respective grant project's principal investigator (PI) and will be a member of the University Library's Software Development Group. Specifically, this position will support and be funded by the following grant project: The Student/Library Collaborative: Toward Transformative Mobile Library Service, funded by The Institute of Museum and Libraries National Leadership Grant. This grant funded position will provide an opportunity to participate in design, development, and testing of innovative, cutting-edge mobile applications. The successful candidate will collaborate with experienced Research Programmers in the Grainger Engineering Library Information Center and the Library's Office of Information Technology Planning and Policy to design and implement an infrastructure and middleware to support the creation of the mobile applications. The responsibilities of this position will include: * developing and/or customizing APIs generated by library data; * designing an infrastructure to support these APIs; * using and/or customizing of commercial APIs; * leading training in using these APIs and developing additional ones; * applying APIs to mobile applications; * troubleshooting, and writing documentation for the process; * developing Web, Windows, and Linux applications and tools; * installing, maintaining, and administering of Web services and other networked applications; * database design, and programming; * collaborating with student groups on mobile application development; * and providing technical assistance to and consultation with Library and other University faculty and staff collaborating on the project. As an Academic Professional, employees are expected to use investigation time to pursue areas of interest, not directly in support of an immediate program need, in accordance with the University Library's policy on Investigation Time for Academic Professional Employees. Some investigations that originate in this manner may evolve into regular work assignments or production activities. See http://www.library.illinois.edu/administration/human/resources/investigationtime.html Environment: The University of Illinois at Urbana-Champaign Library is a leader in the delivery of user services, and active programs in information, instructional, access, and scholarly services help the Library to maintain its place at the intellectual heart of the campus. The Library also holds one of the preeminent research collections in the world, encompassing more than 12 million volumes and a total of more than 23 million items. The Library is committed to maintaining the strongest collections and service programs possible, and to engaging in research, development, and scholarly practice - all of which support the University's missions of teaching, research, and public engagement. The Library employs approximately 90 faculty members, and more than 300 academic professionals, staff, and graduate assistants. For more information, see: http://www.library.illinois.edu/ Qualifications: Required: Bachelor's degree in computer science, computer engineering, or a related field; 3+ years of experience with object oriented programming; experience using modern Web-server development frameworks for creating 'restful' AJAX web services; Experience with source control tools: e.g. git, SVN; Knowledge of XML and XSLT; demonstrable LINUX or UNIX experience; demonstrable knowledge of relational database design principles and programming using SQL; ability to work in a collaborative team environment, and successfully handle multiple priorities; good oral and written communication and customer service skills. Preferred: ALA-accredited Master's degree in library and/or information science (or equivalent); Experience designing and developing mobile apps for either the Android or iPhone platforms; experience in a library IT unit or working with library-specific applications; experience leading technology training; experience with metadata schema including MARC, Dublin Core, RDF, etc.; knowledge of library standards such as MARC, Z39.50, OAI-PMH, or OAI-ORE; experience using web APIs, such as the Amazon, Google Book, or Hathi Trust APIs; experience administering Windows or Linux servers, including web servers; experience applying web application security best practices. Salary: Salary is commensurate with credentials and experience. Terms of Appointment: Twelve month
Re: [CODE4LIB] Metadata
On Thu, Feb 16, 2012 at 7:13 AM, suzanne.pilsk suzanne.pi...@gmail.comwrote: (Pssst: Does it matter if you call it data and I call it metadata?) It may matter only to the extent that we each use the terms appropriately relative to our own use and context. On a related note, I would make a weak initial claim that, relative to an application context, metadata is sufficient if it allows for the data which it described to be used for that specific application. The question of what is the optimal amount of metadata can then be considered to be the point at which the marginal cost of adding more metadata is equal to the expected marginal benefit of adding that metadata across all applications. The calculation is not trivial: both the cost and the benefit of adding a specific metadatum are unlikely to be strictly independent of other metadata; for example, adding an extra title from a work in hand may not cost as much as adding a different set of metadata, but it may not provide as much aggregate value given the presence of the correlated fields. Simon
[CODE4LIB] Job: Software Engineer at Massachusetts Institute of Technology
The MIT Libraries are seeking an experienced, enthusiastic and self-motivated software engineer to join a group of developers that provides programming and software analysis support across the MIT Libraries. This position provides both general application development for library technical platforms and services, as well as specialized development for the MIT Geodata repository. **RESPONSIBILITIES** Reporting to the Head of Software Development and Analysis, the Software Engineer will be responsible for development work, from front-end web applications to back-end data management, for a variety of projects underway in the Libraries. An initial focus will be enhancing GIS software and systems that expand access to geodata through existing services and tools. S/he will work collaboratively with the Senior GIS Specialist, the Geospatial Data Librarian, and the Digital Library Systems Manager to investigate, define, recommend, and build new services around geodata. The Engineer will maintain up-to-date system documentation and manage code in a version-control system. S/he will also advise and consult with library technical and non-technical staff to provide GIS web development expertise and guidance. As a member of the Software Development and Analysis Department, the Software Engineer will work with other software engineers in supporting the ongoing development of the MIT Libraries software infrastructure, including, but not limited to, institutional repositories (DSpace, and others), digital library collection management systems, digital archiving systems (e.g., Archivists' Toolkit), and other digital library systems. S/he will collaborate with other technology partners both on and off-campus. **QUALIFICATIONS** _Required: _Bachelor's degree. Three years of software development experience in a Unix/Linux environment. Demonstrated experience developing and maintaining web applications in a Java development environment (e.g., MVC, Tomcat/Jetty). Demonstrated proficiency in one or more of the following programming languages: Ruby, Python, PHP. Strong working knowledge of XML. Strong relational database experience in one or more of the following: Oracle, PostgreSQL, MySQL. Proven ability to meet deadlines and manage competing priorities. Flexibility and a collaborative approach to innovation, problem solving, and working across organizational boundaries with librarian, faculty, and both technical and non-technical staff. Ability to be productive independently and to work successfully in a team environment within a culturally diverse community. Excellent verbal and written communication skills. _Preferred: _Demonstrated experience with GIS APIs, tools, and platforms, such as ArcSDE, OpenLayers, and GeoServer is strongly preferred. Experience with distributed indexing technology (e.g., Apache Solr) and NoSQL data storage systems. Demonstrated experience designing, developing and/or consuming web services (e.g., XML, JSON). Demonstrated proficiency with Javascript and Javascript libraries/frameworks (e.g., jQuery). Familiarity with open source repository systems such as DSpace, Fedora, and affiliated projects and services such as DuraSpace. Experience working in a library or academic computing environment. **SALARY AND BENEFITS** $65,000 minimum. Actual salary commensurate with qualifications and experience. MIT offers excellent benefits including a choice of health and retirement plans, a dental plan, and tuition assistance. The MIT Libraries afford a flexible and collegial working environment and foster professional growth of staff with management training and travel funding for professional meetings. **APPLICATION PROCESS** Apply online at:[http://hrweb.mit.edu/staffing/](http://hrw eb.mit.edu/staffing/). Please include cover letter, resume, and contact information for three references. Review of applications will beginimmediately and continue until position is filled. MIT is strongly and actively committed to diversity within its community and particularly encourages applications from qualified women and minoritycandidates. Brought to you by code4lib jobs: http://jobs.code4lib.org/job/795/
[CODE4LIB] www.code4lib.org down?
Hi, The code4lib site appears to be unreachable. Anyone know what is going on? Tom Tom Burton-West University of Michigan Library
Re: [CODE4LIB] www.code4lib.org down?
A power outage yesterday at Oregon State University's data center caused all sorts of problems for many systems. Most are back up, but the server running code4lib.org (and the wiki and the planet) hasn't successfully been brought back up yet. That's about all I know at this point. Ryan Wick -Original Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Burton-West, Tom Sent: Thursday, February 16, 2012 11:06 AM To: CODE4LIB@LISTSERV.ND.EDU Subject: [CODE4LIB] www.code4lib.org down? Hi, The code4lib site appears to be unreachable. Anyone know what is going on? Tom Tom Burton-West University of Michigan Library
[CODE4LIB] code4lib.org
I apologize if this has already come up, but has there been any announcement about the code4lib.org drupal and mediawiki outages at Oregon State? //Ed
Re: [CODE4LIB] too much Metadata
Related: http://go-to-hellman.blogspot.com/2009/06/when-are-you-collecting-too-much-data.html On Feb 10, 2012, at 3:57 PM, Patrick Berry wrote: So, one question I forgot to toss out at the Ask Anything session is: When do you know you have enough metadata? You'll know it when you have it, isn't the response I'm looking for. So, I'm sure you're wondering what the context for this question is, and honestly there is none. This is geared towards contentDM or DSpace or Omeka or Millennium. I've seen groups not plan enough for collecting data and I've seen groups that are have been planning so long they forgot what they were supposed to be collecting in the first place. So, I'll just throw that vague question out there and see who wants to take a swing. Thanks, Pat/@pberry
[CODE4LIB] reflections on why i felt super welcome at code4lib
Thanks everyone who helped put on the conference in Seattle last week. Here's my first stab at why I think the code4lib community is awesome: http://www.tararobertson.ca/welcome-to-code4lib/ I was reluctant to go to code4lib in the past, as I’d heard it was a hostile environment for women.While I’ve heard about a couple of crappy incidents in the past, this was by far the most welcoming tech event I have ever been to. I went to Apachecamp during ApacheconNA and there was a lot of discussion about sexual harassment and the Ada Initiative's Anti Harassment policy: http://adainitiative.org/2011/12/example-conference-anti-harassment-policy-turns-one-year-old/ I appreciate the work that people have done to create a culture that is welcoming to women and is about making technology in libraries better. code4lib is a great example of how to proactively nurture the kind of community we want to be in, instead of having to legislate a code of behaviour. Would love to hear your thoughts on this... Cheers, Tara -- tara robertson systems and technical services librarian, library | tel 604 630 4567 emily carr university of art + design http://www.ecuad.ca | 1399 Johnston Street, Vancouver BC V6H 3R9
[CODE4LIB] Programmer Position at UCLA Library
Alright cool folks -- you all will want this position. I mean, there's smog involved -- how can you resist? Seriously, I can say that the UCLA Library is a great place to work and the Digital Library group is very active and engaged. You may have heard that UCLA is in the middle of a migration to the Islandora framework (Fedora + Drupal + cool other pieces), and it's really going to be a great opportunity to help shape this open source digital library solution. Please feel free to email me to learn more about what our groups are up to and what LA and UCLA are like. - Elizabeth Lisa McAulay Librarian for Digital Collection Development UCLA Digital Library Program http://digital.library.ucla.edu/ email: emcaulay [at] library.ucla.edu From: Bermudez, Araceli Sent: Thursday, February 16, 2012 5:02 PM To: All Library Staff Subject: HR UPDATE: Recruitment Initiated for Institutional Repository Project Programmer (Programmer/Analyst III), Library Information Technology- Position Reopened Good Afternoon, The Library has reopened the Institutional Repository Project Programmer (Programmer/Analyst III) position with Library Information Technology to new applicants. The new application deadline is 02/20/12. Thank you. Araceli Working Title (Payroll Title) Department Requisition # NEW Application Deadline Institutional Repository Project Programmer (Programmer/Analyst III) Library Information Technology 16100 02/20/12 The complete posting, which includes the position description, complete qualifications and application procedures, is available on both the UCLA Career Opportunities Website at: https://hr.mycareer.ucla.eduhttps://hr.mycareer.ucla.edu/ and on the UCLA Library Employment and HR Website, at: http://www.library.ucla.edu/about/employment.cfm UCLA staff members are encouraged to forward this information to potential applicants. If you would like to nominate someone for this position, please contact Araceli Bermudez, bermu...@library.ucla.edumailto:bermu...@library.ucla.edu. UCLA Library staff members are also asked to post this position posting to professional LISTSERVs as appropriate (please copy Araceli Bermudez on such postings so we may retain a copy of the postings for reporting purposes). Thank you for your assistance. ** Araceli Bermudez Assistant Director, Staff and Student HR UCLA Library Human Resources 22478 YRL, Box 951575 Los Angeles, CA 90095-1575 (campus mailcode: 157511) voice: (310) 825-7947 fax: (310) 825-6174 bermu...@library.ucla.edu **
[CODE4LIB] CFP - INTERNATIONAL JOURNAL OF COMPUTER SCIENCE AND SECURITY (IJCSS)
CALL FOR PAPERS - INTERNATIONAL JOURNAL OF COMPUTER SCIENCE AND SECURITY (IJCSS) ISSN: 1985-1553 Volume 6, Issue 3 Info. at http://www.cscjournals.org/csc/journals/IJCSS/journal_cfp.php?JCode=IJCSS Computer Science Journals (CSC Journals) invites researchers, editors, scientists scholars to publish their scientific research papers in an International Journal of Computer Science and Security (IJCSS) Volume 6, Issue 3. The Journal of Computer Science and Security (IJCSS) is a refereed online journal which is a forum for publication of current research in computer science and computer security technologies. It considers any material dealing primarily with the technological aspects of computer science and computer security. The journal is targeted to be read by academics, scholars, advanced students, practitioners, and those seeking an update on current experience and future prospects in relation to all aspects computer science in general but specific to computer security themes. Subjects covered include: access control, computer security, cryptography, communications and data security, databases, electronic commerce, multimedia, bioinformatics, signal processing and image processing etc. CSC Journals anticipate and invite papers on any of the following topics: Authentication and authorization models Electronic commerce Bioinformatics Image processing Communications and data security Object Orientation Computer Engineering Operating systems Computer graphics Parallel and distributed processing Computer Networks Programming languages Computer security Robotics Cryptography Signal processing Data mining Software engineering Databases Theory Important Dates - IJCSS CFP - Volume 6, Issue 3. Paper Submission: March 31, 2012 Author Notification: May 15, 2012 Issue Publication: June 2012 For complete details about IJCSS archives publications, abstracting/indexing, editorial board and other important information, please refer to IJCSS homepage. We look forward to receive your valuable papers. If you have further questions please do not hesitate to contact us at cscpr...@cscjournals.org. Our team is committed to provide a quick and supportive service throughout the publication process. A complete list of journals can be found at http://www.cscjournals.org/csc/bysubject.php Sincerely, J. Stewart Computer Science Journals (CSC Journals) B-5-8 Plaza Mont Kiara, Mont Kiara 50480, Kuala Lumpur, Malaysia Tel: + 603 6207 1607, + 603 2782 6991 Fax:+ 603 6207 1697 Url: http://www.cscjournals.org
