resending -my last message appears to have gone out without is message body 



DSPACE 5 now does a lot more with metadata. After the upgrade I see that there 
are two new schemes: 

SELECT * FROM METADATASCHEMAREGISTRY; 

        METADATA_SCHEMA_ID       NAMESPACE                           SHORT_ID   
                                           
        1       http://dublincore.org/documents/dcmi-terms/     dc
        2       http://www.princeton.edu/                       pu
        21      http://purl.org/dc/terms/                       dcterms
        22      http://dspace.org/eperson                       eperson     

There are a good number of related fields for the new schemas: 

SELECT  MF.* FROM METADATAFIELDREGISTRY MF WHERE MF.METADATA_SCHEMA_ID  > 2;

        METADATA_FIELD_ID  METADATA_SCHEMA_ID  ELEMENT
        243             21              abstract
        244             21              accessRights
        245             21              accrualMethod
        ...
        ... 
        296             21              type
        297             21              valid
        298             22              firstname
        299             22              lastname
        300             22              phone
        301             22              language


But when I look into the metadata value table there is not a single related  
value 

SELECT * FROM METADATAVALUE MV WHERE   MV.METADATA_FIELD_ID in 
    (SELECT  MF.METADATA_FIELD_ID FROM METADATAFIELDREGISTRY MF WHERE 
MF.METADATA_SCHEMA_ID  > 2);
no rows selected


This does not feel right - is there a step I overlooked ?  
I sent a question earlier in about version 5 not recognizing an IP group  - see 
enclosed message below. I suspect that this may be a related issue.

Monika

________________
Monika Mevenkamp
phone: 609-258-4161
Lewis Library,Washington Road and Ivy Lane, Princeton University, Princeton, NJ 
08544


> On Mar 10, 2015, at 4:09 PM, Monika C. Mevenkamp 
> <moni...@exchange.princeton.edu> wrote:
> 
> I am upgrading to dspace 5 from 1.8 
> 
> I have ip authentication enabled but the system does not recognize the ip 
> group 
> It looks in the metadata table with 
> 
> 
> DEBUG org.dspace.storage.rdbms.DatabaseManager @ Running query "select * from 
> epersongroup e LEFT JOIN metadatavalue m on (m.resource_id = 
> e.eperson_group_id and m.resource_type_id = ? and m.metadata_field_id = ?) 
> where  dbms_lob.substr(m.text_value) = ?"  with parameters: 6,64,Princeton_IPs
> 
> Looking into my database I see that there is not a single  metadatvalue for 
> resource type 6. 
> I am fairly convinced I could ‘fix’ this by copying values from the 
> EPERSONGROUP table to the metadata value table. Is that what I should do ? 
> Does anybody have a handy UPDATE SQL statement ready to go  ? 
> 
> Monika
> 
> 
> 
> ________________
> Monika Mevenkamp
> phone: 609-258-4161
> Lewis Library,Washington Road and Ivy Lane, Princeton University, Princeton, 
> NJ 08544
________________
Monika Mevenkamp
phone: 609-258-4161
Lewis Library,Washington Road and Ivy Lane, Princeton University, Princeton, NJ 
08544


> On Mar 16, 2015, at 5:36 PM, Monika C. Mevenkamp <moni...@princeton.edu> 
> wrote:
> 

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Reply via email to