Thanks Chris, this really increased my understanding of the CMA. I had
not separated the constraints on the persistence object (Fedora
hasModel) from the constraints and assertions about the domain object
(potentially rdf:type). Since these objects are not 1:1 the same thing
in our system, th
Frank, it looks like you didn't include the '#' sign on the end of the
namespace URL. You will need that.
Greg Jansen
Carolina Digital Library Developer
UNC Chapel Hill
\yf508 wrote:
> Hi all,
>
> I have a problem while dealing with foxml document by using dom4j in our
ther Maven
projects.
thanks for advising,
Greg
__
Greg Jansen
Developer - Carolina Digital Repository
University of North Carolina at Chapel Hill
-
This SF.Net email is sponsored by the Moblin Your Move Developer's chal
erates for
the file if I ingest it through the admin client. Is there a way to
verify that Fedora checksum is the same as mine without finishing the
ingest operation, thereby creating an object with potentially corrupt
data, and comparing afterward?
many thanks,
Greg
___
Greg Jansen
Ca
the repository, such as text
extraction and format conversion.
Greg Jansen
Carolina Digital Repository
Chris Wilper wrote:
> Hi Asger,
>
> This looks like an impressive body of work. Thanks for sharing it
> with us. I will certainly be taking a closer look and would like to
>
Hello Dev list,
I need to update some modules against Fedora 3.3 and later 3.4. I'm
having trouble resolving maven dependencies for third party jars. In
fact, I also cannot reach the releases m2 repository. I can compile
those project locally of course, but still need to reach the third part
ARQL queries against our Fedora triple store. However, we opted
to install Mulgara as a stand-alone application. So we are using the
Mulgara SPARQL REST interface. If you use the Fedora-installed Mulgara,
then you may have a different endpoint.
Greg Jansen
On 02/23/2011 02:47 AM, Laura del
g the
whole request
out.flush();
Is this the expected pathway for a data stream dissemination request? It
seems like even a couple simultaneous small files could fill the heap.
This makes me think I've configured it improperly somehow.
thanks for your help,
Greg Jansen
p.s.
Here is the stack
Hey Fedora Devs,
We're using FeSL on our server and ran into this issue:
https://jira.duraspace.org/browse/FCREPO-1020
I made a patch for it and I'd really like to have anyone with FeSL
experience take a look. We're about to deploy this thing, which seems to
work fine on our test server and def
I think you're right about logging and exception handling being the
first step, along with some refactoring of the long doCommit() method.
We're pushing hundreds of gigabyte WAV files into our Fedora and we have
a modified low-level storage module with it's own failure modes. These
logging impr
I agree with this, as long as the non-canonical stores are updated after
all the canonical stores have a chance to fail.
Greg
On 11/18/2011 03:07 AM, Stephen Bayliss wrote:
> We should try and ensure the integrity of the "canonical datastore".
>
> And maybe in considering any rollback-type behav
11 matches
Mail list logo
