Re: [MCN-L] Guessable web URLs

[Stefano Cossu]

In principle it is best to have completely opaque identifiers for the 
web, and a separate system (which can be a simple as a couple of 
database tables) to keep track of the mapping. This is useful not as 
much for obscuring URLs (security through obscurity may work for 
short-term embargo as in your case, but becomes brittle for permanent 
URLs) as it is for sustainability. If your public URLs contain e.g. a 
TMS and/or NetEx ID, if you migrate out of either system you may not be 
able to retain those identifiers and will break all your public URLs.


Stefano


On 5/2/20 6:46 AM, Heidi Quicksilver wrote:

I’m not sure if this will be helpful or not but I know that there is a way
to create URL‘s that are not predictable. We did this on the last website
that I worked on because we had to create content that was super secret
before it was publicly released and we had people who were scraping our
site to try and figure out what the content was before we released it. We
were working with Gavin and Neil at Cogapp for the web development. Perhaps
they can help explain how they helped us create unpredictable URLs for web
pages. We were using Drupal 8.

Heidi Q
Perez Art Museum Miami
Previously Rock & Roll Hall of Fame
hquicksil...@pamm.org


___
You are currently subscribed to mcn-l, the listserv of the Museum Computer 
Network (http://www.mcn.edu)

To post to this list, send messages to: mcn-l@mcn.edu

To unsubscribe or change mcn-l delivery options visit:
http://mcn.edu/mailman/listinfo/mcn-l

The MCN-L archives can be found at:
http://www.mail-archive.com/mcn-l@mcn.edu/

Re: [MCN-L] Guessable web URLs

[Stefano Cossu]

Emily,
I think others gave very valid suggestion that I mostly agree with, 
especially about separating internal-use images with public ones. These 
should reside in separate servers with clear firewall rules assigned. 
Most importantly, you should isolate your internal management system 
from the WWW. Assume your institution *will* (not *could*) be attacked 
by malicious actors at any time.


I support Jeremy's suggestion to look at IIIF. That takes some setup 
time, as well as the need to produce specific derivatives. However, any 
other image derivative is taken care of by the image server after that. 
No need to manually generate thumbnail, web large/small/medium, etc.


However, a IIIF manifest cannot enforce access to an image, it only 
provides hints for good citizens about which derivatives they should 
request. You can tackle restricted access in the same pipeline that 
generates your IIIF-ready derivatives, by setting up a reduced 
derivative size, or no public derivative at all, for 
copyright-restricted images. This way you will have one folder / 
repository with internal-only access behind firewall, and one open to 
the WWW or behind the image server.


This may sound like a lot to deal with, but in the long run it will 
definitely save you a lot of management time, migration nightmares and 
security loopholes.


Stefano


On 5/1/20 10:41 AM, Jeremy Ottevanger wrote:

Hi Emily,

I'm going to leave for another thread the question of whether or not 
everything "should" be made available to the same degree - it's complex 
and not really what you're asking. But clearly that will be one element 
in people's assessment of whether the risk you're describing should be 
an issue or not.


So, given that rights and licences are clearly important in your 
situation, would I think it a risk to leave a door ajar for people to 
take images you aren't meant to let them have? Well yes, it could be. Do 
I think people are likely to take them and abuse them? It's possible, of 
course, but perhaps it comes down the nature of the risks you want to 
avoid. If you could get into trouble with a rights holder that's one 
thing. But if you have an image licence sales team that is worried about 
lost revenue, I wouldn't worry so much. I don't think any commercial 
customer who is likely to have paid for a licence before is less likely 
to do so just because they figure out how to nick the image without 
paying. At the same time it can be a delicate political situation to get 
as far as you have and release any high-res images, in which case it can 
be canny politics to conspicuously avoid this risk. I've had to play 
this game in the past, even if I wanted to go much faster towards more 
open content, and in the end I believe it's really important to earn the 
trust of your organisation - it makes you a more plausible advocate for 
change anyway.


So if there is a risk, what can you do to mitigate it? The obvious thing 
would be to put the images you want to publish into a separate directory 
to the ones you don't. That probably means having a second copy of them 
- that is surely the easiest solution. But if you can't do this for 
reasons of space (I hope not!) or of managing the process, I can think 
of a couple of other ways, although they could be equally tricky to 
automate or have other drawbacks. If this is a Linux server you could 
sim-link the published images to a location that you use for the web 
directory. Or you could do something clever with file permissions so 
that the web server (Apache or whatever) only has access to the 
published images (or with .htaccess). Both of these solutions could be 
automated, or semi-automated, for example by running a script over a 
list of files you want to sim-link. This might be built into the 
publication process.


Or you could have a think about a IIIF solution (https://iiif.io/). This 
has so many things going for it that go beyond what we're talking about 
here, but one salient point is that you aren't giving people direct 
access to a file - only the IIIF service on your server has access to 
the file, which it then does its magic on and sends out when requested. 
There is a manifest file containing information about the image, and if 
this isn't there then the IIIF service shouldn't return the image. I 
hope someone will correct me if I have that wrong!


The downsides of IIIF would be that, firstly, you might not be 
publishing TIFFs like this, off the top of my head I'm not sure if that 
is supported by the spec or by any IIIF servers. And secondly, you'd 
need a way to publish manifests for each image you published. But once 
you did that you could have all the goodness that comes with IIIF and 
viewers like Mirador (https://projectmirador.org/) or Universal Viewer 
(https://universalviewer.io/)


Good luck with your project, it's good to hear of more high resolution 
images being set free!


All the best,

Jeremy

-
Dr 

Re: [MCN-L] [IIIF-Discuss] Re: MCN 2018 Call for Proposals OPEN thru April 30

[Stefano Cossu]

All,

This is the link to the MCN 2018 project for IIIF-related sessions: 
https://3.basecamp.com/3922322/join/23XtS7WyWfBe


Please join if you are interested in proposing or participating otherwise.


Best,
Stefano


Stefano Cossu
Director of Application Services, Collections

The Art Institute of Chicago
116 S. Michigan Ave.
Chicago, IL 60603
312-499-4026

On 4/16/18 2:15 PM, Rob Lancefield wrote:

Hi Stefano and Tina,

At the IIIF Meetup at Museums & the Web this Thursday, I'm planning to 
mention the idea of a IIIF-oriented proposal for MCN 2018 (not 
necessarily organizing it myself, but seeing if someone wants to run 
with it). I'll be glad to point people wherever would be best for 
that: probably the SIG's Basecamp space, if it's up by then, or the 
Slack channel. And if there's any uptake on the idea at MW, I'll share 
that news here and in Slack.


all best,
Rob

On Monday, April 16, 2018 at 1:48:17 PM UTC-4, tsh...@artic.edu wrote:

Hi Stefano, the next meeting is 5/1, so after the MCN submission
deadline. Perhaps ideas for proposals can be started in this thread?

On Friday, April 13, 2018 at 2:34:30 PM UTC-5, Stefano Cossu wrote:

Hello,
See below.

Can we bring up ideas at the next IIIF Museum Community
meeting? It will
be good to set up Basecamp by then too, so we can discuss
logistics.

Best,
Stefano


 Forwarded Message 
Subject: [MCN-L] MCN 2018 Call for Proposals OPEN thru April 30
Date: Thu, 12 Apr 2018 18:44:48 -0400
From: Eric Longo <er...@mcn.edu>
Reply-To: Museum Computer Network Listserv <mc...@mcn.edu>
To: MCN-L <mc...@mcn.edu>

Call for proposals for MCN 2018 annual conference in Denver is
open now
through April 30!

http://conference.mcn.edu/2018/Submit2018.cfm
<http://conference.mcn.edu/2018/Submit2018.cfm>

Scholarship and volunteer applications also accepted through
April 30.

-
Eric Longo
Executive Director
MCN <http://www.mcn.edu/> (Museum Computer Network)

toll free: +1-888-211-1477 x801
mobile: +1-917-822-7343
er...@mcn.edu

Click here <http://calendly.com/eric-longo
<http://calendly.com/eric-longo>> to schedule a meeting with me.
___
You are currently subscribed to mcn-l, the listserv of the Museum
Computer Network (http://www.mcn.edu)

To post to this list, send messages to: mc...@mcn.edu

To unsubscribe or change mcn-l delivery options visit:
http://mcn.edu/mailman/listinfo/mcn-l
<http://mcn.edu/mailman/listinfo/mcn-l>

The MCN-L archives can be found at:
http://www.mail-archive.com/mcn-l@mcn.edu/
<http://www.mail-archive.com/mcn-l@mcn.edu/>

-- 
Stefano Cossu

Director of Application Services, Collections

The Art Institute of Chicago
116 S. Michigan Ave.
Chicago, IL 60603
312-499-4026

--
-- You received this message because you are subscribed to the 
IIIF-Discuss Google group. To post to this group, send email to 
iiif-disc...@googlegroups.com. To unsubscribe from this group, send 
email to iiif-discuss+unsubscr...@googlegroups.com. For more options, 
visit this group at https://groups.google.com/d/forum/iiif-discuss?hl=en

---
You received this message because you are subscribed to the Google 
Groups "IIIF Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to iiif-discuss+unsubscr...@googlegroups.com 
<mailto:iiif-discuss+unsubscr...@googlegroups.com>.

For more options, visit https://groups.google.com/d/optout.


___
You are currently subscribed to mcn-l, the listserv of the Museum Computer 
Network (http://www.mcn.edu)

To post to this list, send messages to: mcn-l@mcn.edu

To unsubscribe or change mcn-l delivery options visit:
http://mcn.edu/mailman/listinfo/mcn-l

The MCN-L archives can be found at:
http://www.mail-archive.com/mcn-l@mcn.edu/

Re: [MCN-L] open source dams

[Stefano Cossu]

Marin,
We at the Art Institute of Chicago have built LAKE, a DAMS and 
institutional repository based on existing open source software such as 
Fedora and Samvera (formerly Hydra). Our implementation is open source 
too, however not quite ready for straight-forward adoption yet [1].


Hyku [2] is a "turnkey" version of what we did, independently developed 
by Stanford, DPLA and Duraspace based on the same technology. There is a 
live demo available with a relatively simple and general-purpose 
workflow [3].


At the end of the day it all depends on how you plan to use your DAMS, 
and the choices above (or even the choice of an open source solution) 
may or may not be a good fit.



Best,
Stefano

[1] https://github.com/aic-collections/aicdams-lakeshore
[2] http://hydrainabox.samvera.org/ - note the many names—Hydra/Samvera 
is currently undergoing rebranding

[3] https://demo.hydrainabox.org/


On 07/26/2017 08:24 AM, Marin J. Lewis wrote:

Good morning!

We're developing a list of open source dams to explore. Does anyone have any 
recommendations/experiences to share about open source dams that have been adopted by 
the museum community, beyond ResourceSpace<https://www.resourcespace.com/>?

With appreciation,
Marin

___
Marin J. B. Lewis
Collections Information Specialist
Princeton University Art Museum
Princeton, New Jersey 08544
(609) 258-0477 | m...@princeton.edu<mailto:m...@princeton.edu>




___
You are currently subscribed to mcn-l, the listserv of the Museum Computer 
Network (http://www.mcn.edu)

To post to this list, send messages to: mcn-l@mcn.edu

To unsubscribe or change mcn-l delivery options visit:
http://mcn.edu/mailman/listinfo/mcn-l

The MCN-L archives can be found at:
http://www.mail-archive.com/mcn-l@mcn.edu/



--
Stefano Cossu
Director of Application Services, Collections

The Art Institute of Chicago
116 S. Michigan Ave.
Chicago, IL 60603
312-499-4026

___
You are currently subscribed to mcn-l, the listserv of the Museum Computer 
Network (http://www.mcn.edu)

To post to this list, send messages to: mcn-l@mcn.edu

To unsubscribe or change mcn-l delivery options visit:
http://mcn.edu/mailman/listinfo/mcn-l

The MCN-L archives can be found at:
http://www.mail-archive.com/mcn-l@mcn.edu/

[MCN-L] IIIF Museum Interest Group meeting at MW2016

[Stefano Cossu]

Hello,

In preparation to the IIIF community meeting to be held at the MoMA in New York 
City next May [1] we are interested in having a pre-meeting specifically 
targeted at museums. What better opportunity than the Museums and the Web 
conference in April? 

If you are attending MW2016, whether you have just heard about the 
International Image Interoperability Framework (IIIF) [1] or you are deeply 
involved in its development, you are invited to an informal meeting with other 
museum professionals who share this interest. Please fill out and send the 
following form to participate: 

https://docs.google.com/a/artic.edu/forms/d/1jeqk--HCsnpiZqRfGcbVO5LC_ATvSy_YB1M1x_tmq4c/viewform

Goal of this meeting is to assess the museum-specific interests and needs 
related to IIIF and what would be most valuable for them to see at the New York 
meeting. 

Time and place of the MW2016 meeting will be posted once we have an estimated 
attendance. 

Thanks,
Stefano


[1] http://iiif.io/event/2016/newyork/
[2] http://iiif.io

-- 
Stefano Cossu
Director of Application Services, Collections

The Art Institute of Chicago
116 S. Michigan Avenue
Chicago, IL 60603
___
You are currently subscribed to mcn-l, the listserv of the Museum Computer 
Network (http://www.mcn.edu)

To post to this list, send messages to: mcn-l@mcn.edu

To unsubscribe or change mcn-l delivery options visit:
http://mcn.edu/mailman/listinfo/mcn-l

The MCN-L archives can be found at:
http://www.mail-archive.com/mcn-l@mcn.edu/

Re: [MCN-L] LAM Interoperability

[Stefano Cossu]

Hi Sarah,
Good point! Thanks for raising it. I was talking about the Art
Institute of Chicago in case it was not clear.

Stefano


On Mon, 29 Feb 2016 10:00:04 -0500
"Sarah Clark" <scl...@historicrichmondtown.org> wrote:

> For those responding to the interoperability questions, please
> consider naming your institution in your reply.  I'm finding the
> replies very interesting but can't always figure out where they are
> coming from.
> 
> Thanks,
> Sarah
> 
> Sarah Clark
> Curator
> Historic Richmond Town, Staten Island Historical Society
> 441 Clarke Avenue, Staten Island, NY  10306
> 718-351-1611, ext. 272
> www.historicrichmondtown.org
> 
> Explore our collections at:
> http://historicrichmondtown.org/treasures/online-collections-database
> 
> 
> 



-- 
Stefano Cossu
Director of Application Services, Collections

The Art Institute of Chicago
116 S. Michigan Avenue
Chicago, IL 60603
___
You are currently subscribed to mcn-l, the listserv of the Museum Computer 
Network (http://www.mcn.edu)

To post to this list, send messages to: mcn-l@mcn.edu

To unsubscribe or change mcn-l delivery options visit:
http://mcn.edu/mailman/listinfo/mcn-l

The MCN-L archives can be found at:
http://www.mail-archive.com/mcn-l@mcn.edu/

Re: [MCN-L] LAM interoperability SIG

[Stefano Cossu]

Dear Mary,
Thank you for your excellent reading suggestions. 

Your "Metadata for All" paper points out very rightfully one of the main
challenges to achieving our interoperability goals: a legacy that is
very specific to museums, which have never found a practical interest
in standardization. This is understandable due to the different
mission of museums and to the kind of information they handle and how
they use it; but we are now at a point where sharing data is becoming
more and more compelling and adoption of shared standards is key to
this. 

Libraries and archives, as you point out, have been systematically using
standard vocabularies long before digital cataloging became widespread.
Most museums, on the contrary, have been running for decades on
home-brewed ontologies dictated by internal requirements. Changing this
is a big challenge, both on a technical and an adoption level - my
institution is right in the middle of it. 

Maybe the issue is more political than technical, though. Maybe all we
need are some "pioneers" to encourage other museums to move in this
direction. If a group of institutions can put together enough resources
and spearhead the effort to establish some basic patterns, other
institutions with less resources may feel more confident to follow a
path that presents some concrete examples. 

Also, I think that focusing on interoperability within one
institution first is safer, more manageable and more rewarding than
aiming straight at inter-institutional interoperability. A
successful case study of integration between a museum's collections,
library and archives can grant additional confidence from the
stakeholders to pursue interoperability between institutions. 

Thanks,
Stefano


On Tue, 23 Feb 2016 13:05:57 -0800
"M. Elings" <meli...@library.berkeley.edu> wrote:

> Dear Emmanuelle,
> 
> This is a topic that I and my colleague Günter Waibel spent many years
> exploring. I wanted to share an old but relevant article we wrote on
> this topic: Metadata for All
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__firstmonday.org_article_view_1628_1543.=AwMFaQ=-dg2m7zWuuDZ0MUcV7Sdqw=e507lsOLMLpNWxMc9GIaKxb-mxZhbMJ1mY6SLgDKU0A=Mhq2GJdm6RCb7I4xZTxatQop6A7djdAQVYIHSGR9HU4=ov_2jIFIc4rPdGcMGS-xgtDJ1LG7pzgTbFZ-f8x2ieo=>,
> which discusses the reasons behind our inability to have our data
> interoperate or "play nicely" with other institutions. It is also a
> useful history of efforts that came before and what worked and what
> didn't.
> 
> 
> 
> I think the promise of linked data and efforts like Europeana and
> DPLA have shown us what is possible when we use network level
> standards, which allow our data to reach outside the confines of our
> local institutional systems. I don't think we will ever get to a
> point where we all follow the same metadata practices but we can
> extract and share our data in ways that are more universal.
> 
> 
> 
> Other readings of interest:
> 
> Beyond the Silos of the LAMs: Collaboration Among Libraries, Archives
> and Museums
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.oclc.org_content_dam_research_publications_library_2008_2008-2D05.pdf=AwMFaQ=-dg2m7zWuuDZ0MUcV7Sdqw=e507lsOLMLpNWxMc9GIaKxb-mxZhbMJ1mY6SLgDKU0A=Mhq2GJdm6RCb7I4xZTxatQop6A7djdAQVYIHSGR9HU4=z55EXfGSEjjjNvVPZWDVTh6KOIgVilCfAJHUQamMGSI=>
> 
> 
> Think Global, Act Local – Library, Archive and Museum Collaboration
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.oclc.org_content_dam_research_publications_library_2009_waibel-2Derway-2Dmmc.pdf=AwMFaQ=-dg2m7zWuuDZ0MUcV7Sdqw=e507lsOLMLpNWxMc9GIaKxb-mxZhbMJ1mY6SLgDKU0A=Mhq2GJdm6RCb7I4xZTxatQop6A7djdAQVYIHSGR9HU4=X7xWGNlemcwO553CQv7fslJzCX5171zrQ3e9N25y_Ko=>
> 
> 
> 
> Good luck moving the topic forward! As technology moves ahead, these
> things will be easier to achieve. There also needs to a powerful
> incentive, such as better serving user needs. We are getting there...
> incrementally.
> 
> 



-- 
Stefano Cossu
Director of Application Services, Collections

The Art Institute of Chicago
116 S. Michigan Avenue
Chicago, IL 60603
___
You are currently subscribed to mcn-l, the listserv of the Museum Computer 
Network (http://www.mcn.edu)

To post to this list, send messages to: mcn-l@mcn.edu

To unsubscribe or change mcn-l delivery options visit:
http://mcn.edu/mailman/listinfo/mcn-l

The MCN-L archives can be found at:
http://www.mail-archive.com/mcn-l@mcn.edu/

Re: [MCN-L] LAM interoperability SIG

[Stefano Cossu]

Hi there, 

1. At the moment we are not exchanging data with other institutions in a
"smart" way. The recent work on our new DAMS will bring more
opportunity in this direction though. The key for this is having adopted
RDF as the lingua franca for our DAMS. 

Before we tackle inter-institutional interoperability, we want to
better connect departments within the museum and heterogeneous data
sets such as library, archives and collections. This will have more
obvious and immediate advantages for us. 

2. CIDOC CRM seems to be the most comprehensive and flexible ontology
to encompass the widest range possible of cultural heritage items.
However, CIDOC CRM cannot be practically used as a cataloging ontology,
but rather as a harmonization tool. It should sit between the cataloger
and the consumer, and accessed only to machines that can handle its full
complexity. 

There are several publishing schemata that map to CIDOC-CRM and expose
only the concepts meaningful to a human end user. There is not, as far
as I know, a cataloging schema that is encoded in RDF and maps to CIDOC
CRM. I am aware of ongoing efforts to serialize the Getty's AAT (which
contains CDWA terms) into RDF [1], but having a separate, formalized
cataloging ontology based on CDWA would be a great advancement in this
area. 

3. We use Fedora [2] which is completely content-agnostic and allows to
build any sort of content model. Fedora and its satellite
projects encourage the use of PCDM [3] as a very basic and
broad-scoped ontology on top of which more domain-specific ontologies
can be layered to satisfy any kind of content modeling. 

4. My team (5 people) is in charge of designing and implementing our
collection information systems. A separate department, Digital
Experience and Access, acts as a broker for end users' (staff and
public) needs and is in constant dialog with us. I act as an
interpreter who translates semi-technical requirements into
specifications. 


[1] http://www.getty.edu/research/tools/vocabularies/lod/index.html
[2] http://fedorarepository.org 
[3] https://github.com/duraspace/pcdm/wiki

On Thu, 18 Feb 2016 16:33:51 +
"Delmas-Glass, Emmanuelle" <emmanuelle.delmas-gl...@yale.edu> wrote:

> Dear all,
> 
> In order to get us started with the LAM interoperability SIG, we
> would like to get your feedback on a few questions.
> 
> 1. Use cases: as a museum, library or archive, whenever you tried to
> integrate your data with other institutions, what worked, what
> didn't, and why?
> 
> 2. Interoperable metadata schemas and/or ontologies: what is out
> there that can help bring collection data and bibliographical data
> together? What do you think about them, what are the challenges and
> how do you plan or wish to utilize them?
> 
> 3. Existing interoperability tools: what software platforms do you
> use? If you could design your own, what would they be? 
> 
> 4. Staffing: what staff member(s) usually work together on these
> questions of data interoperability at your institution (list titles)?
> What new staff position(s) would be useful?
> 
> If you could give brief replies that would be great. The goal is to
> assess the challenges of our community as well as the opportunities.
> This common base should lead to some interesting discussions that we
> could bring up in an in-person meeting at the next MCN conference in
> New Orleans.
> 
> Emmanuelle and Stefano
> 
> Emmanuelle Delmas-Glass
> Collections Data Manager
> Collections Information & Access Department
> Yale Center for British Art
> http://britishart.yale.edu
> 203-410-4069
> --
> Stefano Cossu
> Director of Application Services, Collections
> The Art Institute of Chicago
> 116 S. Michigan Avenue
> Chicago, IL 60603
> 
> 
> 
> 
> 



-- 
Stefano Cossu
Director of Application Services, Collections

The Art Institute of Chicago
116 S. Michigan Avenue
Chicago, IL 60603
___
You are currently subscribed to mcn-l, the listserv of the Museum Computer 
Network (http://www.mcn.edu)

To post to this list, send messages to: mcn-l@mcn.edu

To unsubscribe or change mcn-l delivery options visit:
http://mcn.edu/mailman/listinfo/mcn-l

The MCN-L archives can be found at:
http://www.mail-archive.com/mcn-l@mcn.edu/

Re: [MCN-L] data archiving

[Stefano Cossu]

Matt,
Have you looked into the Digital Preservation Network [1]? It is a
project still in development but they have an interesting billing plan
and are aiming specifically at cultural heritage data. 

Best,
Stefano

[1] http://www.dpn.org/


On Wed, 13 Jan 2016 12:00:01 +
mcn-l-requ...@mcn.edu wrote:

> Send mcn-l mailing list submissions to
>   mcn-l@mcn.edu
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>   http://mcn.edu/mailman/listinfo/mcn-l
> or, via email, send a message with subject or body 'help' to
>   mcn-l-requ...@mcn.edu
> 
> You can reach the person managing the list at
>   mcn-l-ow...@mcn.edu
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of mcn-l digest..."
> 
> 
> Today's Topics:
> 
>1. Re: data archiving (Matt Wheeler) (Glen Barnes)
> 
> 
> --
> 
> Message: 1
> Date: Wed, 13 Jan 2016 09:54:26 +1300
> From: Glen Barnes 
> To: mcn-l@mcn.edu
> Subject: Re: [MCN-L] data archiving (Matt Wheeler)
> Message-ID:
>   

Re: [MCN-L] LAM interoperability SIG?

[Stefano Cossu]

Dominic,
Thanks for your outstanding report on the activities around 
interoperability.


I agree that CIDOC-CRM is gaining popularity. It is also great to know 
that there is an OWL serialization for it [1].


How do you see CIDOC-CRM compared to FRBRoo in terms of bridging the gap 
between cultural heritage disciplines?


I also strongly agree with your point about abstraction. One of the 
topics that we touched in our session was that CIDOC-CRM, while being 
extremely flexible, is also hardly usable by humans on a daily basis. 
Since collection managers and librarians cannot catalog records using 
these models directly, we need an abstraction layer to map cataloging 
ontologies into the broader CIDOC-CRM. I would love to see, e.g. a RDF 
serialization of CDWA(I think that there is some effort in that 
direction with CONA[2]). I am curious to see what you and the Swedish 
National Archives are doing in this regard.


Also, if you want a human-readable publishing platform (website, mobile 
app, etc.) you need another layer that maps these broad models to 
something more fit for human consumption, e.g. dcterms, VRA core, or 
such. CIDOC-CRM can be used for cross-institutional interoperability or 
search/query APIs where you want to retain the full complexity of the 
model.


Thanks,
Stefano

[1] http://erlangen-crm.org/
[2] http://www.getty.edu/research/tools/vocabularies/cona/about.html

On 11/17/2015 12:56 PM, mcn-l-requ...@mcn.edu wrote:

Message: 2
Date: Tue, 17 Nov 2015 17:58:36 +
From: Dominic Oldman
To:"mcn-l@mcn.edu"  
Subject: [MCN-L]  LAM interoperability SIG?
Message-ID:

Re: [MCN-L] mcn-l Digest, Vol 123, Issue 12

[Stefano Cossu]

Hi Eric,
Following up the discussion on this list[1], I would like to propose a 
LAM interoperability SIG and would encourage any interested colleagues 
to propose themselves as chairs.


Is it something that can be accommodated? I know timing is tight!

Thanks,
Stefano

[1] http://www.mail-archive.com/mcn-l@mcn.edu/msg10052.html



On 11/14/2015 06:00 AM, mcn-l-requ...@mcn.edu wrote:

Message: 2
Date: Fri, 13 Nov 2015 14:15:06 -0500
From: Eric Longo<e...@mcn.edu>
To: MCN-L<mcn-l@mcn.edu>
Subject: [MCN-L] Call for SIG Chairs candidates
Message-ID:
<CABMmy_ThTUtTAbJ+=cveavqjsxockfucg5b7aybzmcxjqrn...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi everyone
For the first time in MCN?s history since revising the SIG Charter
<http://mcn.edu/wp-content/uploads/2015/10/SIGs-Charter_2014_FINAL.pdf>
last year, we will hold virtual elections between December 1-15, 2015 to
elect SIG Chairs and Vice Chairs. These volunteer positions have so far
been held by leaders who were appointed in their role by MCN's Board given
the previous process.

As a reminder, MCN Special Interest Groups (SIGs) are organized and run by
MCN members who have shared interests related to MCN?s overall mission.
Each SIG provides a forum for MCN members to pursue specific interests and
niche topics. You'll find the names of the current SIG Chairs by perusing
each SIG page on our website
<http://mcn.edu/community/special-interest-groups-sigs/>. All are
professionals who have particular expertise or interest in a SIG's area.

In addition to being active in the community, chairing a SIG also
constitutes a leadership development opportunity. We invite anyone who
might be interested in the opportunity to let their intent known to the
current leaders of each SIG *no later than Friday November 20, 2015 by 12pm
ET*.

The list of candidates will be prepared and shared via online ballot forms
so everyone can participate in electing next year's SIG Chairs and Vice
Chairs. The voting will take place from December 1 through December 15,
2015. A reminder will be emailed to all.

At the end of the voting period, the ballots will be counted and the two
top candidates that receive the most votes in each SIG will be elected
Chair and Vice-Chair for a one-year term, renewable indefinitely.

We hope you will participate in electing our SIG leaders.

Any questions, please feel free to ask me or Scott Sayre, MCN Board SIGs
Liaison.
Best,
eric

-
Eric Longo
Executive Director
Museum Computer Network<http://www.mcn.edu/>
O: +1-888-211-1477 x801
M: +1-917-740-6631
e...@mcn.edu

Help ease email overload<http://emailcharter.org/>.

--


--

Stefano Cossu
Director of Application Services, Collections

The Art Institute of Chicago
116 S. Michigan Ave.
Chicago, IL 60603
312-499-4026

___
You are currently subscribed to mcn-l, the listserv of the Museum Computer 
Network (http://www.mcn.edu)

To post to this list, send messages to: mcn-l@mcn.edu

To unsubscribe or change mcn-l delivery options visit:
http://mcn.edu/mailman/listinfo/mcn-l

The MCN-L archives can be found at:
http://www.mail-archive.com/mcn-l@mcn.edu/

Re: [MCN-L] LAM interoperability SIG?

[Stefano Cossu]

Hi Amalyah,
Although I have found Google groups very easy to set up and manage, I 
have no strong opinion on which platform this discussion should be hosted.


My main point here is whether we should keep the discussion in the main 
MCN list or on a separate one. The reason for the latter choice would be 
to help involving librarians and archivists not directly concerned with 
other museum technology topics. Maybe a sub-list within the mcn-l would 
be possible?


Given the broad audience who joined this thread only from the MCN list 
within a short time, however, I don't think this is a critical issue at 
the moment.


Thanks,
Stefano


On 11/18/2015 06:00 AM, mcn-l-requ...@mcn.edu wrote:

Message: 4
Date: Wed, 18 Nov 2015 09:48:06 +
From: Amalyah Keshet<akes...@imj.org.il>
To: Museum Computer Network Listserv<mcn-l@mcn.edu>
Subject: Re: [MCN-L] LAM interoperability SIG?
Message-ID:<74af28f834f34dea85a254803d937...@mailsrv2.imj.org.il>
Content-Type: text/plain; CHARSET=US-ASCII

Stefano:

The MCN listserv is the perfect place to discuss this.  That's what it exists 
for.  Anyone can join, it's open and uncomplicated.  Google groups and such are 
more complicated (rather a pain, in fact, sometimes), and not everyone has the 
time and patience to log into multiple platforms every day.  The best, most 
highly professional, international discussion groups I (for one) belong to are 
all listservs.

Amalyah Keshet



--

Stefano Cossu
Director of Application Services, Collections

The Art Institute of Chicago
116 S. Michigan Ave.
Chicago, IL 60603
312-499-4026

___
You are currently subscribed to mcn-l, the listserv of the Museum Computer 
Network (http://www.mcn.edu)

To post to this list, send messages to: mcn-l@mcn.edu

To unsubscribe or change mcn-l delivery options visit:
http://mcn.edu/mailman/listinfo/mcn-l

The MCN-L archives can be found at:
http://www.mail-archive.com/mcn-l@mcn.edu/

[MCN-L] Full-time application developer at the Art Institute of Chicago

[Stefano Cossu]

All,

The Art Institute of Chicago is seeking a Senior Application Developer 
to work on their digital asset management system, called LAKE.


LAKE is a groundbreaking effort from a major museum to embrace 
standards-based, community-driven open source software to build its core 
data repository. This position offers plenty of learning and growth 
opportunities as well as a great team to collaborate with.


Ideally the candidate will have experience with the Fedora repository 
and Hydra, but we welcome any fast-learning and highly motivated 
candidate with a solid experience with Ruby, Python 3, Java, RDF and 
semantic stores.


See attached job description for details. Apply at 
https://hrweb.artic.edu/psc/HRPRODE/EMPLOYEE/HRMS/c/HRS_HRAM.HRS_APP_SCHJOB.GBL?FOCUS=Applicant=PORTAL_ROOT_OBJECT.HC_HRS_CE_GBL2=false=FolderPath%2cIsFolder 
(job ID: 8961) or contact me in person (scossu at art ic period edu) for 
technical questions.


Thank you,
Stefano Cossu


--

Stefano Cossu
Director of Application Services, Collections

The Art Institute of Chicago
116 S. Michigan Ave.
Chicago, IL 60603
312-499-4026



8961-FT-LAKE_dev.pdf
Description: Adobe PDF document
___
You are currently subscribed to mcn-l, the listserv of the Museum Computer 
Network (http://www.mcn.edu)

To post to this list, send messages to: mcn-l@mcn.edu

To unsubscribe or change mcn-l delivery options visit:
http://mcn.edu/mailman/listinfo/mcn-l

The MCN-L archives can be found at:
http://www.mail-archive.com/mcn-l@mcn.edu/

Re: [MCN-L] LAM interoperability SIG?

[Stefano Cossu]

All,
Thank you so much for your interest and for the very insightful 
contributions.


Given the large number of interested parties, I am wondering if we 
should kick off a separate mailing list (Google groups or such) so we 
can more easily reach out to other communities. I still think that we 
can target the next MCN conference for an in-person meeting, while we 
distill ideas in the mailing list.


Thoughts?

Stefano


On 11/17/2015 12:56 PM, mcn-l-requ...@mcn.edu wrote:

--

Stefano Cossu
Director of Application Services, Collections

The Art Institute of Chicago
116 S. Michigan Ave.
Chicago, IL 60603
312-499-4026

___
You are currently subscribed to mcn-l, the listserv of the Museum Computer 
Network (http://www.mcn.edu)

To post to this list, send messages to: mcn-l@mcn.edu

To unsubscribe or change mcn-l delivery options visit:
http://mcn.edu/mailman/listinfo/mcn-l

The MCN-L archives can be found at:
http://www.mail-archive.com/mcn-l@mcn.edu/

[MCN-L] LAM interoperability SIG?

[Stefano Cossu]

Hello,
It was exciting to host a lively conversation at the last MCN conference 
about Libraries, Archives and Museums (topics: [1]; slides: [2]). I am 
happy to see that many colleagues are interested in tearing down the 
barriers between bibliographical, archival and collection records within 
museums, as well as promoting the exchange of information and 
technologies between Cultural Heritage institutions.


I think the session sparked quite some interest and raised important 
topics from many of the participants. I also believe that this 
conversation needs to be brought forward.


This mailing list may be a good place to follow up that conversation. I 
would love to propose a similar session for next MCN, actually even 
closer to a round-table discussion than to a panel.


If enough people are interested, I would also propose to create a 
special interest group for this topic. Goal of the SIG would be torefine 
the core topics that we brought up at the conference using this mailing 
list, and then meet in person at the next MCN with a distilled down list 
of action items.


Anyone interested in this proposal is welcome to respond.

Thanks,
Stefano

[1] http://sched.co/3tND
[2] 
http://www.slideshare.net/StefanoCossu/librarries-archives-museums-discussion-mcn-2015

--

Stefano Cossu
Director of Application Services, Collections

The Art Institute of Chicago
116 S. Michigan Ave.
Chicago, IL 60603
312-499-4026

___
You are currently subscribed to mcn-l, the listserv of the Museum Computer 
Network (http://www.mcn.edu)

To post to this list, send messages to: mcn-l@mcn.edu

To unsubscribe or change mcn-l delivery options visit:
http://mcn.edu/mailman/listinfo/mcn-l

The MCN-L archives can be found at:
http://www.mail-archive.com/mcn-l@mcn.edu/