-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 4/19/06 11:51 AM, Beth Kirschner wrote:
>
Do you want to export _all_ content from Sakai (e.g. chats,
>
schedules, assignments, ...), or simply the content in Resources?
Two parts of an answer to your question. The first part is that we're
not thinking of "export" -- more like "supplant". The line of reasoning
is like this: learning objects, assignments, chat records, etc. are all
digital objects (if we define a "digital object" to mean zero or more
datastreams with associated descriptive metadata). Those digital
objects can be used in more than one context -- for instance:
* an article published through a peer-review electronic interface
using the same underlying Fedora repository is visible as a
resource to Sakai users
* a dataset added to a community's institutional repository
interface using the same underlying Fedora repository is visible
as a resource to Sakai users
* a paper submitted as part of an assignment can be used as part
of an ePortfolio (one outside of a Sakai-embedded OSP, of course)
This line of reasoning also helps answer the second part, which is any
digital object that could be repurposed we want to put directly into the
Fedora repository. (See "On the Need for a General Purpose Digital
Object Repository"
http://dltj.org/2006/01/general-purpose-repository/
for a more in-depth discussion.)
>
We've been working on a proof-of-principle sakai-fedora-tool. that
>
allows users to browse, search and edit a Fedora Repository from
>
within Sakai. The authentication/authorization between Sakai and
>
Fedora would be shared, as described in the "Fedora Authorization
>
with XACML Policy Enforcement" (which references OhioLINK's
>
Shibboleth servlet filter in http://www.fedora.info/download/2.1/
>
userdocs/server/security/AuthorizationXACML.htm#ATTR3).
That is one of the key points of friction...n-tier "delegated" access
management with Shibboleth. It is expected to be addressed in version
2.2 of Shib.
>
I wasn't thinking of using Shibboleth, but using the Sakai user
>
directory in place of the Tomcat-user attributes that Fedora uses by
>
default.
I think there would still need to be another login step, for although
the user database itself can be shared the authentication realms are
quite different. (That is where an n-tier Shibboleth will come in very
handy...)
>
The sakai-fedora-tool is not well documented at this point, but
>
the idea is to support a flexible data model (targeted for eResearch)
>
defined by using XML Schema Files. I've attached a screenshot. Feel
>
free to contact me offline if you want to talk about this some more.
>
This might be an alternative that is feasible in your proposed
>
timeframe.
I'd very much like to see your team's work. Perhaps we could arrange a
conference call or a video conference off-list?
Peter
- --
Peter Murray
http://www.pandc.org/peter/work/
Assistant Director, Multimedia Systems tel:+1-614-728-3600;ext=338
OhioLINK: the Ohio Library and Information Network Columbus, Ohio
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (Darwin)
Comment: Using GnuPG with Mozilla -
http://enigmail.mozdev.org
iD8DBQFERpfA4+t4qSfPIHIRAmfJAKCwHC2O05novC96oS+Wpg+PlSidOwCfYJGz
YBQrFw/aNhBbkJasa913+I0=
=esQQ
-----END PGP SIGNATURE-----
----------------------
This automatic notification message was sent by Sakai Collab
(
http://collab.sakaiproject.org/portal) from the DG: Development site.
You can modify how you receive notifications at My Workspace > Preferences.
Thread at a glance:
Previous Message by Date:
click to view message preview
Re: Sakai 2.2 status
Glenn R. Golden wrote:
test-harness has been removed from mini (it has dependencies on
non-mini things). You might need to delete it locally after an update.
Ahh, right. That's an interesting problem... since the test harness
needs all of sakai's APIs to launch the component manager, it can't be
part of sakai-mini and support sakai-max at the same time. I think I'll
add a test-harness branch specifically for the mini distro.
Josh
--
Josh Holtzman
Educational Technology Services, UC Berkeley
jholtzman@xxxxxxxxxxxx
510.643.7380
----------------------
This automatic notification message was sent by Sakai Collab
(http://collab.sakaiproject.org/portal) from the DG: Development site.
You can modify how you receive notifications at My Workspace > Preferences.
Next Message by Date:
click to view message preview
svn external warning for Sakai
I just did something seemingly innocent that ended up loosing a lot
of work. I'm not quite sure what happened, but perhaps it will
become more clear when I explain it. I think that this is something
we need to watch out for.
I checked out the sakai/trunk. This had an older version of the site
module.
Since I was working on the site module, I deleted the site files
locally and checked out svn/site/trunk site. Now I have the latest
in-progress site files in-place with the sakai 2.2. code.
After *much* work, and *many* changes made to site files, I was
getting ready to check in - but I wanted to make sure all was well
against the latest code - so I ran this command from my dev folder:
svn update
Usually, this is a great thing to do, as it updates all the code you
have, leaving your changes alone. But in this case, when it got to
the site files, it wiped out most of my work. This is because it was
updating the site module from the externals definition, which was a
different state of the repo. than I had actually checked out in the
site folder.
I'm not quite sure what it did, but it seemed to revert most of the
files to the previous version, and deleted much of my new work. It
happened so fast...
I think the same thing could happen if you have a branch of your
project that you are working on, and you, like I did, place it among
the Sakai 2.2 files. This again sets up a condition where update
from the root will use the externals definition, but your files are
from some other part (another branch) of the repo.
If I had done an update from site, it would have been fine. I think
the problem was that I did it from the root.
This is not a problem if you are working on the trunk of your
project - then update and status work great from the root.
So, if you have a module that is not part of the svn:externals of the
distribution, but have the files in the distribution, and if the
distribution might think that your files belong to it... watch out.
- Glenn
Glenn R. Golden
Software Architect, University Of Michigan
ggolden@xxxxxxxxx
----------------------
This automatic notification message was sent by Sakai Collab
(http://collab.sakaiproject.org/portal) from the DG: Development site.
You can modify how you receive notifications at My Workspace > Preferences.
Previous Message by Thread:
click to view message preview
Sakai Fedora Tool
Peter,
Do you want to export _all_ content from Sakai (e.g. chats,
schedules, assignments, ...), or simply the content in Resources?
We've been working on a proof-of-principle sakai-fedora-tool. that
allows users to browse, search and edit a Fedora Repository from
within Sakai. The authentication/authorization between Sakai and
Fedora would be shared, as described in the "Fedora Authorization
with XACML Policy Enforcement" (which references OhioLINK's
Shibboleth servlet filter in http://www.fedora.info/download/2.1/
userdocs/server/security/AuthorizationXACML.htm#ATTR3). I wasn't
thinking of using Shibboleth, but using the Sakai user directory in
place of the Tomcat-user attributes that Fedora uses by default.
The sakai-fedora-tool is not well documented at this point, but
the idea is to support a flexible data model (targeted for eResearch)
defined by using XML Schema Files. I've attached a screenshot. Feel
free to contact me offline if you want to talk about this some more.
This might be an alternative that is feasible in your proposed
timeframe.
- Beth
[see attachment: "sakai-fedora-tool.tiff", size: 80678 bytes]
On Apr 19, 2006, at 9:11 AM, Peter Murray wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
At OhioLINK, we're considering posting an idea to create some glue
between Sakai and Fedora such that any content that comes into
Sakai is
ingested into the Fedora repository and any content in the Fedora
repository is visible to Sakai. After looking at the Sakai
architecture
a bit, a project of this type is considerably more complex that I
originally thought. And it may not be doable with today's
technology --
in particular I'm thinking we'll need the n-tier Shibboleth capability
to pass credentials between Sakai and Fedora. Opinions as to the
wisdom
of proposing this project -- particularly along the lines of comments
about how it could or could not be achieved in a June to August
timeframe -- would be most welcome.
Peter
On 4/19/06 8:18 AM, Knoop, Peter wrote:
While the Sakai Foundation is not explicitly listed -- our mentoring
resources are pretty well tapped out at the moment -- at least one
partner school, Portland State University, lists Sakai in its
suggested
project areas. If there are others out there with available
mentoring
resources who are interested in doing this, please don't hesitate to
sign your institution up!
-peter
-----Original Message-----
From: Stephen Marquard [mailto:marquard@xxxxxxxxxxxxxx]
Sent: Tuesday, April 18, 2006 3:25 PM
To: sakai-dev@xxxxxxxxxxxxxxxxxxxxxxx
Subject: Google summer of code
Google's summer of code is running again:
http://code.google.com/summerofcode.html
Shouldn't we be in there? :-)
Cheers
Stephen
--
Stephen Marquard
Learning Technologies Co-ordinator, Centre for Educational
Technology
Centre for Higher Education Development, University of Cape Town
Email: marquard@xxxxxxxxxxxxxx IM: xmpp:marquard@xxxxxxxxxxxxxx
Cell: +27-83-500-5290
----------------------
This automatic notification message was sent by Sakai Collab
(http://collab.sakaiproject.org/portal) from the DG: Development
site.
You can modify how you receive notifications at My Workspace >
Preferences.
----------------------
This automatic notification message was sent by Sakai Collab
(http://collab.sakaiproject.org/portal) from the DG: Development
site.
You can modify how you receive notifications at My Workspace >
Preferences.
- --
Peter Murray http://www.pandc.org/peter/work/
Assistant Director, Multimedia Systems tel:+1-614-728-3600;ext=338
OhioLINK: the Ohio Library and Information Network Columbus, Ohio
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFERjcV4+t4qSfPIHIRAgXgAKCidl4RMN4ZaNzJ/h/yy1pHeZ0RxgCeOUis
wrbbfkVNcC9wvX4psZpQYwU=
=8HtC
-----END PGP SIGNATURE-----
----------------------
This automatic notification message was sent by Sakai Collab
(http://collab.sakaiproject.org/portal) from the DG: Development site.
You can modify how you receive notifications at My Workspace >
Preferences.
Attachments:
sakai-fedora-tool.tiff
http://collab.sakaiproject.org/access/content/attachment/2fdda46a-e2d2-42d4-0032-b3364e9d7acb/sakai-fedora-tool.tiff
----------------------
This automatic notification message was sent by Sakai Collab
(http://collab.sakaiproject.org/portal) from the DG: Development site.
You can modify how you receive notifications at My Workspace > Preferences.
Next Message by Thread:
click to view message preview
Setting the current user id in 2.2
I'm trying to update the test-harness in 2.2, and I'm having difficulty
"logging in" to sakai.
Here's what used to work for me:
Session session = SessionManager.getCurrentSession();
session.setUserId("admin");
session.setUserEid("admin");
But now calling UserDirectoryService.getCurrentUser().getId() returns an
empty string. And when I try to take actions such as adding users,
adding sites, etc, I get a PermissionException, since user is null.
I've even tried AuthzGroupService.refreshUser("admin"), but that doesn't
fix this either. Does anyone have any ideas what I need to do to set
the current userID in 2.2?
Thanks,
Josh
--
Josh Holtzman
Educational Technology Services, UC Berkeley
jholtzman@xxxxxxxxxxxx
510.643.7380
----------------------
This automatic notification message was sent by Sakai Collab
(http://collab.sakaiproject.org/portal) from the DG: Development site.
You can modify how you receive notifications at My Workspace > Preferences.