I don’t think DSpace really supports metadata to that level of 
multi-dimensionality.

Metadata on an item in DSpace is meant to directly describe that item. So for a 
property, you could have property.seller and property.buyer – or for more 
granularity, you could have:

property.seller.name
property.seller.address
property.seller.phone
etc

These could even be repeatable fields – but if you have eg:

property.seller.name = Jo Bloggs
property.seller.name = Sam Christie
property.seller.address = 123 Main St
property.seller.address = 64 High St

DSpace has no way of knowing which name belongs to which address. As far as 
DSpace is concerned the metadata values don’t have any relationship to each 
other – only to the item.

At this point I would strongly suggest taking a step back and looking for some 
other software that lets you create a proper relational database.

Deborah

From: [email protected] <[email protected]> On Behalf Of 
Arunendra M. Biswas
Sent: Friday, 2 August 2019 7:21 PM
To: DSpace Technical Support <[email protected]>
Subject: [dspace-tech] Re: Non-bibliographic metadata

So, I have created a separate schema for storing property details (Dspace1.png 
screenshot attached).
The problem is: For a property, there can be 2 parties, E.g. Seller and Buyer. 
Each party can have 1 to N persons, i.e 3 Sellers and 2 Buyers.
We have created a customized submission form for this purpose where 1st page 
describes the registration details, 2nd page-person details, 3rd page-property 
details.
For N persons, I entered details of 1 person, with "Add"-ing for next person 
every time.
This is very complex. (Dspace_prop2.png attached).

Is there any other way? Like generating a person page, on demand only. If 
there's one person, only one "Person"-page(page 2) will appear.If there are 
more than 1 persons, so many times page 2 will appear.

On Wednesday, June 12, 2019 at 1:39:21 PM UTC+5:30, Arunendra M. Biswas wrote:
Can DSpace be used as DMS for non-library situations?For e.g,my client, a 
property dealer maintains details of persons,selling/buying a property and 
details(perimeter,no. of rooms,address) of the property.
Should I just rename the similar fields in the corresponding messages file or 
create a separate schema altogether?
Since Title/Accession Code does not exist in case of property, such mandatory 
fields will have no value in this case.
Suggest please.
--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: 
https://duraspace.org/about/policies/code-of-conduct/<https://duraspace.org/about/policies/code-of-conduct/>
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
[email protected]<mailto:[email protected]>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/f051a5a2-fbf4-40c4-a29b-deeccd9504d6%40googlegroups.com<https://groups.google.com/d/msgid/dspace-tech/f051a5a2-fbf4-40c4-a29b-deeccd9504d6%40googlegroups.com?utm_medium=email&utm_source=footer>.

________________________________

"The contents of this e-mail (including any attachments) may be confidential 
and/or subject to copyright. Any unauthorised use, distribution, or copying of 
the contents is expressly prohibited. If you have received this e-mail in 
error, please advise the sender by return e-mail or telephone and then delete 
this e-mail together with all attachments from your system."

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/SY3PR01MB1307622DB04DBE9C3D8AB13FC5DA0%40SY3PR01MB1307.ausprd01.prod.outlook.com.

Reply via email to