OJS OCS OMP OHS

You are viewing the PKP Support Forum | PKP Home Wiki



Subscriber Import into OJS

Are you an Editor, Author, or Journal Manager in need of help? Want to talk to us about workflow issues? This is your forum.

Moderators: jmacgreg, michael, vgabler, John

Forum rules
This forum is meant for general questions about the usability of OJS from an everyday user's perspective: journal managers, authors, and editors are welcome to post questions here, as are librarians and other support staff. We welcome general questions about the role of OJS and how the workflow works, as well as specific function- or user-related questions.

What to do if you have general, workflow or usability questions about OJS:

1. Read the documentation. We've written documentation to cover from OJS basics to system administration and code development, and we encourage you to read it.

2. take a look at the tutorials. We will continue to add tutorials covering OJS basics as time goes on.

3. Post a question. Questions are always welcome here, but if it's a technical question you should probably post to the OJS Technical Support subforum; if you have a development question, try the OJS Development subforum.

Subscriber Import into OJS

Postby radjr » Wed Jul 24, 2013 3:37 pm

Good Day.

I am looking for documentation on the subscriber import function for OJS. I have exported users with the export function and the export data seems limited. I would prefer to start with a defined import spec and also import from CSV format versus XML. Thanks in advance for any thoughts. Best, Rich D.
radjr
 
Posts: 48
Joined: Thu Jan 17, 2013 1:19 pm

Re: Subscriber Import into OJS

Postby radjr » Wed Jul 24, 2013 3:43 pm

I stumbled upon the dtd for the import function as posted below which is great. Question is are these all the defined fields in the import spec or are there other fields? For example, many foreign addresses have two address lines. Many academic addresses have a department or secondary address line. The Company line looks like it is defined as the affilliation..but this is a tenuous assumption. So, hopefully there is a fuller specification of subscriber import fields and support for CSV format files. Thank you! Rich D.

<!--
* users.dtd
*
* DTD for user information.
* Used by the user import/export functionality.
*
* Usernames and passwords are optional and will be generated automatically if omitted.
*
* $Id: users.dtd,v 1.7 2008/06/10 19:12:09 asmecher Exp $
-->

<!ELEMENT users (user*)>
<!ELEMENT user (username?, password?, salutation?, first_name, middle_name?, last_name, initials?, gender?, affiliation?, signature?, email, url?, phone?, fax?, mailing_address?, country?, interests*, biography*, locales?, role*)>
<!ELEMENT username (#PCDATA)>
<!ELEMENT password (#PCDATA)>
<!ATTLIST password change (true|false) "false">
<!ATTLIST password encrypted (plaintext|md5|sha1) #IMPLIED>
<!-- How the password is encrypted (if applicable).
Encrypted assumes it was encrypted by Validation::encryptCredentials()
and is using the same encryption algorithm used by the system.
Default is "plaintext" (unencrypted). -->
<!ELEMENT salutation (#PCDATA)>
<!ELEMENT first_name (#PCDATA)>
<!ELEMENT middle_name (#PCDATA)>
<!ELEMENT last_name (#PCDATA)>
<!ELEMENT initials (#PCDATA)>
<!ELEMENT gender (#PCDATA)>
<!ELEMENT affiliation (#PCDATA)>
<!ELEMENT signature (#PCDATA)>
<!ATTLIST signature
locale CDATA #IMPLIED>
<!ELEMENT email (#PCDATA)>
<!ELEMENT url (#PCDATA)>
<!ELEMENT phone (#PCDATA)>
<!ELEMENT fax (#PCDATA)>
<!ELEMENT mailing_address (#PCDATA)>
<!ELEMENT country (#PCDATA)>
<!ELEMENT interests (#PCDATA)>
<!ATTLIST interests
locale CDATA #IMPLIED>
<!ELEMENT biography (#PCDATA)>
<!ATTLIST biography
locale CDATA #IMPLIED>
<!ELEMENT locales (#PCDATA)>
<!ELEMENT role EMPTY>
<!ATTLIST role
type (manager|editor|sectionEditor|layoutEditor|reviewer|copyeditor|proofreader|author|reader|subscriptionManager) #REQUIRED>
radjr
 
Posts: 48
Joined: Thu Jan 17, 2013 1:19 pm

Re: Subscriber Import into OJS

Postby asmecher » Wed Jul 24, 2013 3:49 pm

Hi Rich,

That's the entire set of fields. Multi-line addresses are supported -- just put a carriage return in between the lines to separate them as usual. We used Affiliation rather than Company because academic users are more often associated with universities rather than companies.

Regards,
Alec Smecher
Public Knowledge Project Team
asmecher
 
Posts: 7704
Joined: Wed Aug 10, 2005 12:56 pm

Re: Subscriber Import into OJS

Postby radjr » Wed Jul 24, 2013 4:27 pm

Thanks Alec.

A couple of follow-on questions please.
1) Are there no start or end (expiration) date fields for the subscripion..or did I miss them?
2) Are there no subscription type fields? eg individual, institution, etc
3) Are the "subscribers" coded as "reader" in the existing "type" field?
4) How are IP addresses passed?

Lastly, most institutional librarians will manage the IP addresses for their sub types. How does that take place on OJS? I could not find that in the documentation.

Thanks, Rich D.
radjr
 
Posts: 48
Joined: Thu Jan 17, 2013 1:19 pm

Re: Subscriber Import into OJS

Postby asmecher » Wed Jul 24, 2013 5:34 pm

Hi Rich,

Those are subscriber concerns -- there's not yet support for subscription information in the user import/export plugin. (See http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=4064). Subscribers will need to be created through the UI or entered into the DB directly.

Regards,
Alec Smecher
Public Knowledge Project Team
asmecher
 
Posts: 7704
Joined: Wed Aug 10, 2005 12:56 pm


Return to OJS Editorial Support and Discussion

Who is online

Users browsing this forum: Bing [Bot], Google [Bot] and 1 guest
http://pkp.sfu.ca/support/forum/viewtopic.php?p=40044
pkp.sfu.ca
crawl=CC-MAIN-2014-15
29012
application/http; msgtype=response
sha1:ECH7QHWWB6VACS32W6FCI5XRKGYCX7GK
<urn:uuid:e5e2ed74-df83-4a1d-bae7-2a21a3c7caee>
2014-04-17T17:09:04Z
142.58.129.159
sha1:CVTJ5EBGC4XHPJQJQGBQTHF326KESLKK
<urn:uuid:b00a23d5-58c6-4ab2-a6a2-a89514811811>
http://pkp.sfu.ca/support/forum/viewtopic.php?p=40044
length
response
<urn:uuid:0541b838-a1d8-4002-9a93-71b02dd4e87a>
robots: classic
hostname: ip-10-147-4-33.ec2.internal
software: Nutch 1.6 (CC)/CC WarcExport 1.0
isPartOf: CC-MAIN-2014-15
operator: CommonCrawl Admin
description: Wide crawl of the web with URLs provided by Blekko for April 2014
publisher: CommonCrawl
format: WARC File Format 1.0
conformsTo: http://bibnum.bnf.fr/WARC/WARC_ISO_28500_version1_latestdraft.pdf